CORAA
AI Modules/Working Papers/Borrowings
SA 501/505 · Borrowings· पत्र

Borrowings

Secured / Unsecured / Long-term / Overdraft schedule with lender-level reconciliation, a shared interest-rate bridge that ties to the Finance Cost caption by construction, debit-balance flags, and the short-vs-long-term and current-maturity split.

CORAA working paper exported to firm Excel template

Borrowings composes the Secured, Unsecured, Long-term, and Overdraft schedule with reconciliation carried down to the specific lender, not just a lump total, so the working paper shows exactly which lender each figure belongs to. An interest-rate bridge connects this schedule to the Finance Cost caption in the P&L, and both papers are built from the same underlying rate and balance data, so a borrowings schedule and a finance-cost schedule can never silently disagree with each other on the same loan; they return identical numbers by construction, not by a separate reconciliation step bolted on afterward. Loan accounts sitting in debit, which shouldn't happen for a borrowing, are flagged rather than netted quietly into the total. The schedule also carries the short-term vs long-term split and the current-maturity-of-long-term-debt split required for presentation.

  • Secured / Unsecured / Long-term / Overdraft schedule, composed by category
  • Lender-level reconciliation, traces to specific lenders, not just a lump total
  • Shared interest-rate bridge to the Finance Cost P&L caption, both papers built from the same data so they can't silently disagree on the same loan
  • Debit-balance borrowings, a loan account sitting in debit, flagged as an exception
  • Short-term vs long-term split, plus the current-maturity-of-long-term-debt split
  • Cited to SA 501/505
Two paths, one ledger

The old way, and ours.

Two paths to the same audit conclusion. One leaves traces; the other doesn't.

Traditional

The old way

  • -Borrowings schedule and the Finance Cost note built separately, by different preparers, with reconciliation, if any, done after both are drafted
  • -Reconciliation often stops at a lump total rather than tracing to specific lenders
  • -A debit balance on a loan account gets absorbed into the net borrowings figure rather than flagged as unusual
  • -Short-term/long-term and current-maturity splits recomputed by hand each year
Build time: a day, split across two preparers for the loan schedule and the finance-cost note, with a real risk the two quietly disagree on the same loan.
CORAA

On the Ledger

  • Secured/Unsecured/Long-term/Overdraft schedule composed with reconciliation down to the individual lender
  • Finance Cost caption built from the same rate and balance data as the borrowings schedule, so the two tie by construction
  • Debit-balance loan accounts flagged automatically as an exception
  • Short-term/long-term and current-maturity splits computed directly from the schedule
Build time: instant. The borrowings schedule and the finance-cost note are built from one shared source, so they can't quietly disagree.
How it works

Three steps. Every trace logged.

Step 01

Category schedule, lender-level reconciliation

Every borrowing is composed into its Secured, Unsecured, Long-term, or Overdraft bucket, and reconciliation is carried down to the individual lender rather than stopping at a category total, so each figure traces to a specific loan account.

Step 02

Shared interest-rate bridge to Finance Cost

The interest rate and balance data behind the borrowings schedule is the same data feeding the Finance Cost caption in the P&L. Because both papers are built from one shared source, a borrowings figure and its corresponding finance cost can never silently drift apart, they tie by construction, not by a bolted-on reconciliation.

Step 03

Debit-balance flags and the term splits

Loan accounts sitting in debit, which shouldn't happen for a borrowing, are flagged rather than netted into the total. The schedule also produces the short-term vs long-term split and the current-maturity-of-long-term-debt split needed for presentation.

Inside the module

What you actually get.

Category schedule: Secured / Unsecured / Long-term / Overdraft

Every borrowing ledger is composed into its category, with CY/PY columns, forming the base schedule the rest of the working paper builds on.

  • Secured, Unsecured, Long-term, and Overdraft buckets
  • CY and PY columns per category
  • Bucket assignment reads from the ledger classification
  • Feeds the short-term/long-term and current-maturity splits

Lender-level reconciliation

Reconciliation traces down to the specific lender behind each borrowing figure, not just a category lump total, so the auditor can see exactly which loan account a number belongs to.

  • Traces to individual lenders, not a lump total
  • Lender-wise CY/PY movement
  • Drill from category total to lender to ledger
  • Cited to SA 501/505

Shared interest-rate bridge to Finance Cost

The borrowings schedule and the Finance Cost P&L caption are built from the same underlying interest-rate and balance data, so the two are constructed to return identical numbers rather than being reconciled after the fact.

  • One shared rate/balance source feeds both schedules
  • Borrowings and Finance Cost tie by construction
  • No separate bolt-on reconciliation step needed
  • Any drift would be a data issue, not a reconciliation gap

Debit-balance flags and term splits

Loan accounts in debit are flagged as an exception, and the schedule produces the short-term vs long-term split along with the current-maturity-of-long-term-debt figure required for presentation.

  • Debit-balance loan accounts flagged, never silently netted
  • Short-term vs long-term split
  • Current-maturity-of-long-term-debt split
  • Flags carried into the working paper's exceptions
Frequently asked

Answers, up front.

No, by design. Both papers are built from the same underlying interest-rate and balance data, so they're constructed to return identical numbers for the same loan rather than being reconciled as a separate step afterward.
No. CORAA flags the debit-balance loan account as an exception with the figures behind it. Whether it's a temporary overpayment, a data error, or something else is the auditor's judgment call.
Down to the individual lender behind each figure, not just the Secured/Unsecured/Long-term/Overdraft category total, so a reviewer can trace any number back to the specific loan account it came from.
See it on a real ledger

Run borrowings on one of your engagements.

Bring a Trial Balance and a General Ledger. We'll walk through working papers end-to-end on your data, not a sandbox.

Start the free trial →
Borrowings Working Paper | Lender Reconciliation, Finance Cost Tie | CORAA