Popular reconciliation template
Due To vs Due From Reconciliation
Reconcile Due To and Due From balances across entities, branches, group companies, related parties, ledgers, invoices, payments, advances, debit notes, credit notes, journals, taxes, and open items in one structured workflow.
View demo reportReconcile Due To and Due From balances across entities
Due To and Due From accounts should mirror each other across related entities, branches, departments, or group companies. In practice, timing differences, missing entries, incorrect references, manual journals, taxes, currency differences, and wrong allocations often create unreconciled balances.
The Due To vs Due From Reconciliation template helps finance, accounting, controllership, shared services, consolidation, and audit teams compare amounts payable by one entity with amounts receivable by another entity.
This helps teams answer questions such as:
- Which Due To entries correctly match Due From entries?
- Which Due To entries are missing from the corresponding Due From ledger?
- Which Due From entries are missing from the corresponding Due To ledger?
- Which intercompany invoices, payments, advances, reimbursements, allocations, debit notes, credit notes, and journal entries match correctly?
- Which balances differ because of timing, tax, withholding, exchange rate, rounding, bank charges, or accounting treatment?
- Which balances are true open items and which are only timing differences?
- Which Due To / Due From balances should be cleared, adjusted, reclassified, written back, or carried forward?
- Which entries need entity follow-up, branch follow-up, intercompany adjustment, journal correction, approval, or audit review?
This template is useful for multi-entity companies, group companies, holding-subsidiary structures, branch networks, shared service centers, finance teams, controllers, CFOs, auditors, and accounting firms that need a repeatable Due To and Due From reconciliation process.
Required files for this template
Cointab's ready-made workflow is designed around Due To ledgers, Due From ledgers, intercompany ledgers, branch ledgers, related-party ledgers, ERP exports, journal reports, payment reports, invoice registers, debit note files, credit note files, bank statements, and supporting finance data.
| Data source | Example records |
|---|---|
| Due To Ledger | Used as the payable-side source containing entity names, related-party accounts, voucher numbers, transaction dates, posting dates, document numbers, descriptions, debit amounts, credit amounts, balances, currencies, tax values, and accounting status. |
| Due From Ledger | Used as the receivable-side source containing corresponding receivable entries, invoices, payments, advances, reimbursements, debit notes, credit notes, journal postings, balances, references, currencies, and accounting status. |
| Intercompany Invoice Register | Optional, but useful where invoice numbers, invoice dates, entity names, tax values, invoice amounts, document references, and posting references need to be compared with Due To and Due From ledgers. |
| Debit Note / Credit Note Register | Optional, but useful where debit notes, credit notes, reversals, cost allocations, recoveries, corrections, write-backs, and intercompany adjustments need to be matched. |
| Journal Voucher Report | Optional, but useful where manual journals, accruals, provisions, reversals, reclassifications, eliminations, and consolidation entries affect Due To and Due From balances. |
| Payment / Receipt Report | Optional, but useful where intercompany payments, receipts, settlements, reimbursements, advances, repayments, fund transfers, and clearing entries need to be compared. |
| Bank Statement | Optional, but useful where Due To / Due From settlements need to be traced to actual bank debits, bank credits, UTRs, and bank references. |
| Foreign Currency / Exchange Rate File | Optional, but useful where Due To and Due From balances are maintained in different currencies or where exchange gain/loss and revaluation differences need to be analyzed. |
| Tax / Withholding Report | Optional, but useful where GST, VAT, TDS, withholding tax, service tax, tax reversal, input/output tax, or other statutory values affect intercompany balances. |
| ERP / Accounting Export | Optional, but useful if Due To and Due From records are maintained in SAP, Oracle, NetSuite, Microsoft Dynamics, Tally, Zoho Books, QuickBooks, or another accounting system. |
| Supporting Data | Optional supporting files can be used for entity mapping, branch mapping, related-party mapping, cost center mapping, GL mapping, document mapping, invoice mapping, tax mapping, currency mapping, project mapping, department mapping, or other enrichment. |
What Cointab matches in Due To vs Due From reconciliation
Cointab compares Due To and Due From records across document references, debit-credit values, dates, balances, currencies, taxes, payments, journals, and open items.
Due To and Due From entries
Match payable-side Due To entries with corresponding receivable-side Due From entries.
Entity and related-party references
Compare entity codes, company codes, branch codes, related-party names, intercompany account codes, customer/vendor references, and mapped party names.
Document references
Compare invoice numbers, voucher numbers, journal voucher numbers, debit note numbers, credit note numbers, payment references, receipt references, bank references, UTRs, and ERP document numbers.
Debit and credit values
Compare debit amounts in one ledger with corresponding credit amounts in the other ledger, and vice versa.
Intercompany invoices
Match intercompany invoices, recharge invoices, expense allocations, management fees, service charges, transfer entries, branch allocations, and internal billing entries.
Debit notes and credit notes
Compare debit notes, credit notes, corrections, reversals, recoveries, write-backs, intercompany adjustments, and settlement adjustments.
Payments and receipts
Match payments recorded by one entity with receipts recorded by the other entity, including bank transfers, advances, settlements, reimbursements, and clearing entries.
Advances and recoveries
Compare intercompany advances, funding entries, recoveries, repayments, employee recharge entries, branch funding, and cross-entity settlements.
Journal entries
Compare manual journals, accruals, provisions, reversals, reclassifications, eliminations, and consolidation entries.
Balances
Compare opening balances, period movements, closing balances, entity-wise balances, GL-wise balances, branch-wise balances, and currency-wise balances.
Dates and timing
Compare transaction date, document date, invoice date, posting date, payment date, bank date, settlement date, and accounting period.
Currency and exchange differences
Compare transaction currency, base currency, exchange rate, converted amount, exchange gain/loss, and revaluation difference where available.
Taxes and statutory values
Compare GST, VAT, service tax, TDS, withholding tax, tax reversal, input tax, output tax, taxable value, and statutory deductions where applicable.
Accounting classifications
Compare GL account, ledger account, cost center, branch, entity code, project code, department, business unit, narration, and accounting treatment.
Common Due To vs Due From reconciliation exceptions
Cointab helps finance teams focus on unresolved balance differences instead of manually reviewing every intercompany invoice, payment, debit note, credit note, journal, tax entry, and ledger movement.
Due To entry not found in Due From
A payable-side entry appears in the Due To ledger, but no matching receivable-side entry is found in the Due From ledger.
Due From entry not found in Due To
A receivable-side entry appears in the Due From ledger, but no matching payable-side entry is found in the Due To ledger.
Debit-credit mismatch
A debit entry in one ledger does not match the corresponding credit entry in the other ledger.
Amount mismatch
Document references match, but transaction amounts differ.
Balance mismatch
Opening balance, period movement, or closing balance does not agree between Due To and Due From ledgers.
Invoice mismatch
An intercompany invoice exists on one side but is missing, duplicated, reversed, or recorded differently on the other side.
Debit note mismatch
A debit note is recorded in one ledger but missing or incorrectly recorded in the corresponding ledger.
Credit note mismatch
A credit note is recorded in one ledger but missing or incorrectly recorded in the corresponding ledger.
Payment mismatch
A payment recorded by one entity does not match the receipt or settlement entry recorded by the other entity.
Advance mismatch
An advance, prepayment, funding transfer, or intercompany recovery is recorded differently across both ledgers.
Journal mismatch
A manual journal, accrual, reversal, reclassification, provision, or elimination entry exists on one side but not the other.
Timing difference
A transaction is posted in one ledger during the selected period but appears in the corresponding ledger in another period.
Tax mismatch
GST, VAT, TDS, withholding tax, tax reversal, or statutory deduction differs across Due To and Due From records.
Currency mismatch
Transaction currency, exchange rate, converted amount, revaluation amount, or exchange gain/loss differs between both ledgers.
Rounding difference
Small differences exist because of decimal rounding, tax rounding, currency conversion, or system-level rounding.
Duplicate entry
The same invoice, payment, journal, debit note, credit note, voucher, or settlement entry appears more than once.
Wrong entity allocation
A transaction is mapped to the wrong entity, company, branch, department, related party, or business unit.
Wrong GL or cost center allocation
A transaction is posted to the wrong GL account, ledger account, cost center, project, department, or classification.
Narration mismatch
Both entries may relate to the same transaction, but descriptions or narrations are inconsistent.
Missing or unclear reference
Invoice number, voucher number, journal number, payment reference, entity code, related-party name, bank reference, or narration is missing, incomplete, or inconsistent.
Skipped record
A row cannot be reconciled because required data is missing, invalid, duplicate, incomplete, or unusable.
How this ready-made reconciliation works
Cointab pre-configures the workflow so your team does not need to rebuild Due To and Due From reconciliation every period.
Select the template
Choose Due To vs Due From Reconciliation from popular reconciliations.
Select the period
Choose the month, quarter, financial year, consolidation period, audit period, close period, lifetime period, or custom period you want to reconcile.
Upload Due To and Due From ledgers
Upload the Due To ledger, Due From ledger, and any required invoice register, debit note register, credit note register, journal report, payment report, bank statement, tax report, ERP export, currency file, or supporting data.
Validate file format
Cointab checks whether the uploaded files match the expected structure and highlights missing or incorrect columns.
Run reconciliation
Cointab applies predefined data preparation and matching logic for document references, debit-credit values, invoices, payments, journals, debit notes, credit notes, taxes, currencies, balances, and accounting classifications.
Review output
View fully matched, partially matched, unmatched, timing-difference, balance-difference, duplicate, and skipped records.
Download or automate
Download the Excel report, or automate future data input and output through email, SFTP, or APIs.
Structured matching first, AI assistance for difficult cases
Cointab applies structured reconciliation logic first, then uses AI to help with difficult open records where fixed rules are not enough.
Structured matching
Structured matching can use:
Matching scenarios
One-to-one
One Due To entry matches one corresponding Due From entry.
One-to-many
One Due To entry maps to multiple Due From entries, such as invoice plus tax lines, payment plus bank charges, or one journal split across multiple GL lines.
Many-to-one
Multiple Due To entries are grouped and matched against one Due From entry, such as multiple invoices settled through one payment.
Many-to-many
Multiple invoices, payments, debit notes, credit notes, journals, tax lines, advances, and settlement entries across both ledgers are grouped and compared together.
Partial matching
References match, but amount, date, tax value, currency, GL account, related-party mapping, or status differs.
Debit-credit matching
Debit entries in one entity are compared with corresponding credit entries in the other entity.
Balance-level matching
Opening balances, period debits, period credits, period movement, and closing balances are compared entity-wise, GL-wise, branch-wise, or currency-wise.
Timing-difference matching
Transactions posted in different periods are identified and separated from unresolved differences.
Entity and branch matching
Transactions are grouped and compared by entity, branch, company code, related-party code, cost center, or business unit.
Currency matching
Foreign currency amount, base currency amount, exchange rate, revaluation amount, and exchange differences are compared where applicable.
Tax-level matching
Taxable values, tax amounts, withholding, deductions, reversals, and statutory fields are compared where available.
Net and contra matching
Invoices, payments, debit notes, credit notes, advances, reimbursements, recoveries, journal adjustments, reversals, write-backs, and balances are netted where required.
AI-assisted transaction matching
After structured rules run, AI helps match difficult open transactions where:
- References are incomplete
- Voucher numbers are formatted differently
- Invoice numbers are written differently across ledgers
- Narrations are inconsistent
- Entity names are abbreviated or spelled differently
- Related-party names do not match exactly
- One ledger uses debit/credit signs differently
- One transaction is split into multiple lines
- Multiple small entries match one larger balance
- Tax and base amount are posted separately
- Bank references are missing
- Journal entries use different descriptions
- Currency differences require context
- Amounts require business interpretation
- Multiple possible matches exist
AI exception analysis
For transactions that remain open, AI can help identify possible reasons such as:
AI assists matching and exception review, but Cointab keeps reconciliation transparent, reviewable, and audit-friendly.
Audit-ready Due To vs Due From reconciliation reports
Cointab gives your team a clear report showing which Due To and Due From records matched, partially matched, remained unmatched, were timing differences, had balance differences, or were skipped.
Report categories
Fully matched
Transactions where Due To and Due From records match by reference, debit-credit value, amount, date, and status.
Partially matched
Records where references match but amount, date, tax, currency, GL account, entity mapping, or posting status differs.
Unmatched in Due To
Due From records that do not clearly match Due To ledger entries.
Unmatched in Due From
Due To records that do not clearly match Due From ledger entries.
Debit-credit differences
Records where debit and credit treatment does not align across both ledgers.
Balance differences
Records where opening balance, period movement, closing balance, or ledger total differs.
Timing differences
Transactions posted in different periods across Due To and Due From accounts.
Invoice differences
Intercompany invoice records that are missing, duplicated, reversed, or mismatched.
Debit note and credit note differences
Debit notes, credit notes, reversals, and adjustment entries requiring review.
Payment and receipt differences
Payments, receipts, advances, settlements, reimbursements, and clearing entries requiring review.
Journal differences
Manual journals, accruals, provisions, reversals, eliminations, and reclassifications requiring review.
Tax differences
GST, VAT, TDS, withholding, taxable value, and tax reversal differences requiring review.
Currency and exchange differences
Foreign currency, exchange rate, converted amount, exchange gain/loss, revaluation, and rounding differences requiring review.
Accounting classification differences
Wrong entity, branch, GL account, cost center, department, project, related party, or business unit allocation.
Skipped
Records excluded due to missing, invalid, duplicate, incomplete, or unusable data.
Report capabilities
- Summary cards
- Entity-level filters
- Related-party filters
- Branch-level filters
- GL-level filters
- Cost center filters
- Project filters
- Document-level filters
- Invoice filters
- Payment filters
- Journal filters
- Tax filters
- Currency filters
- Difference amounts
- Balance view
- Open-item view
- Timing-difference view
- Matched transaction drill-down
- Manual match
- Undo manual match
- Excel export
- Audit-friendly output
Automate recurring Due To and Due From reconciliation
Once this workflow is stable, Cointab can automate file input, reconciliation runs, and output delivery.
Bring data into Cointab
Data can be received or pulled through:
Run automatically
Schedule reconciliation:
Push output back
Send reconciliation output to:
- Matched Due To / Due From entries
- Matched intercompany invoices
- Matched debit notes
- Matched credit notes
- Matched payments
- Matched journals
- Unmatched Due To records
- Unmatched Due From records
- Debit-credit differences
- Balance differences
- Timing differences
- Currency differences
- Tax differences
- Duplicate entries
- Wrong entity allocation records
- Wrong branch allocation records
- Wrong GL allocation records
- Open items
- Suggested actions
- Excel reconciliation report
- Structured API output
View a Due To vs Due From demo report
See how Cointab presents Due To and Due From reconciliation output with matched, partially matched, unmatched, timing-difference, balance-difference, and skipped records.
Due To vs Due From Reconciliation Demo
Explore a sample report showing intercompany invoices, payments, debit notes, credit notes, journals, advances, balances, tax differences, timing differences, currency differences, and open items.
View demo reportExplore related intercompany and ledger reconciliations
Cointab supports other intercompany, entity, books, ledger, bank, vendor, customer, ERP, and finance reconciliation workflows.
Entity A Ledger vs Entity B Ledger
Reconcile one entity's ledger with another entity's ledger across intercompany invoices, payments, debit notes, credit notes, journals, balances, and open items.
View templateIntercompany Reconciliation
Reconcile intercompany transactions, invoices, debit notes, credit notes, payments, journals, and balances across entities.
View templateBooks Reconciliation
Reconcile accounting books across ledgers, reports, ERP exports, bank records, invoices, payments, and open items.
View templateBank Statement vs Books
Compare bank statement entries with accounting or books records.
View templateVendor Ledger vs Vendor Statement
Reconcile vendor ledgers with vendor statements across invoices, payments, debit notes, credit notes, deductions, and open items.
View templateCustomer Ledger vs Customer Statement
Reconcile customer ledgers with customer statements across invoices, receipts, credit notes, debit notes, deductions, and open items.
View templateBuilt for teams reconciling Due To and Due From balances
This template is useful for teams that regularly reconcile Due To accounts, Due From accounts, intercompany balances, related-party balances, branch balances, journal postings, payments, taxes, currencies, and open items.
Group companies
For groups reconciling Due To and Due From balances between parent, subsidiary, associate, branch, or related-party entities.
Holding and subsidiary structures
For teams comparing intercompany receivables, payables, recharges, advances, recoveries, funding entries, and closing balances.
Multi-entity businesses
For finance teams handling multiple legal entities, business units, cost centers, regions, departments, or branches.
Branch networks
For businesses reconciling head-office vs branch, branch vs branch, entity vs branch, and internal funding balances.
Shared service centers
For shared service teams preparing recurring Due To / Due From and intercompany reconciliation reports.
Finance teams
For teams reconciling related-party balances during month-end, quarter-end, year-end, consolidation, and audit.
Accounting teams
For teams matching intercompany invoices, payments, journals, debit notes, credit notes, tax entries, and balance movements.
Controllers
For controllers who need visibility into open intercompany items, timing differences, balance mismatches, wrong allocations, and posting issues.
CFOs
For finance leaders who want stronger control over intercompany balances, group reporting, consolidation readiness, audit readiness, and financial close accuracy.
Treasury teams
For teams reviewing intercompany settlements, advances, repayments, reimbursements, funding transfers, and bank movements.
Tax teams
For teams reviewing intercompany tax values, withholding, GST, VAT, related-party entries, and statutory deductions.
Auditors
For audit teams reviewing entity-wise balances, related-party confirmations, intercompany confirmations, open items, and supporting transaction trails.
Accounting firms
For CA, CPA, or outsourced accounting teams handling intercompany, multi-entity, branch, related-party, Due To / Due From, and books reconciliation for multiple clients.
Trusted by teams handling Due To and Due From reconciliation
Cointab is used by finance and operations teams that reconcile high-volume, multi-source transaction data across entities, ledgers, Due To accounts, Due From accounts, ERP systems, banks, invoices, payments, journals, books, and internal systems.
“We have worked on many softwares but we love the ease of using cointab. The staff and support is very instant. They are approachable, proficient and patient. Team is very cooperative with the customisations. The experience of using cointab was nice.”
Due To vs Due From Reconciliation FAQs
Start Due To vs Due From Reconciliation
Use Cointab's ready-made Due To and Due From reconciliation workflow to match intercompany invoices, debit notes, credit notes, payments, journals, advances, taxes, balances, currency differences, review exceptions, and export audit-ready reports.
View demo reportReady-made workflow · Reusable every period · Manual upload and automation supported