oraHow It WorksSet Up Once. Save Time Every Reporting Period.
One sitting to set up your facility, with CORA reading your agreement and files. After that, each reporting period is upload, review and sign.
oraHow It WorksOne sitting to set up your facility, with CORA reading your agreement and files. After that, each reporting period is upload, review and sign.
Enter your company and contact details, then secure your account with a password and your authenticator, which is also how you sign. Then the company: its legal name, its address, and who your lender reaches.
There is no sales call and no implementation project to coordinate.
Give the facility a name. Then add the files you already have: the credit agreement, the certificate workbook you send today, and your last reporting package. That is the whole form.
CORA reads the agreement in full and the reporting files beside it, then builds the facility setup: what the agreement defines, what it tests, what it asks you to deliver and when. It calculates the first borrowing base from the source figures in your package and compares the result with your workbook.
Each term carries its clause. Each difference between your workbook and CORA's calculation is named, sized and explained.
The setup comes back as sections: Documents, Terms, Structure, Covenants, Advance rates, Eligibility, First borrowing base, Calendar and requests, Layout. Your screens are on the left. CORA is docked on the right.
Ask what a covenant means, look into a difference or update a detail. Answer the questions CORA could not settle from the documents, each with its options. Confirm changes as you go, with a record of each decision.
Sign to confirm the setup, with a second signer if your company requires one. The facility is active: the structure, the covenants, the rules and the reporting deadlines stand as you approved them, and CORA uses them to prepare each reporting period ahead.
The period opens on your calendar when it is due. From there, six steps on one screen, and CORA does the calculating.
The screen shows what is expected and what has arrived. Add the files and CORA classes each one.
Every line calculated from your source figures under the confirmed rules, the covenants tested, the differences flagged.
Each difference explained in plain words. Resolve it, or note why it stands, with a record of the decision.
One signature or two. The certificate renders as a signed PDF with your name, title and time.
The workbook with CORA's sheet, the signed certificate, the supporting files and a read-me, in one zip.
Send the package the way you always have, then record it as sent: to whom, when, which files.
Sign the completed certificate directly on CORA, with a second signer if your company requires one. No printing, no scanning, no separate e-sign tool.
A company that signs alone signs alone, and the certificate says so. A company that wants four eyes names a second signer, and the certificate waits for both. You choose under Administration and can change it later.
Every signature asks for a fresh code from the signer's authenticator at the moment of signing. The act is on the record with the person, the session and the time.
The certificate's figures and face, then a signatures block: each signer's name, title and time, the method, and the record's own identifiers so the document can always be matched to the run that produced it.