Reporting, Integration, and Period Close
This domain tests how you extract Receivables data, load data from external systems, and close the Receivables period cleanly before GL close.
Reporting and integration
Standard reports include the aging reports, transaction register, receipt register, and journal entry reports. OTBI supports ad hoc analysis, and BI Publisher supports formatted operational reports. Integration options include FBDI for bulk loads of invoices, customers, and receipts, REST services for real-time transactions, and interface tables for AutoInvoice. An FBDI load is a two-step process: load the file to the interface tables with Load Interface File for Import, then run the relevant import job.
Period close
Close Receivables before GL. The practical sequence is to ensure all transactions are complete, apply and reconcile receipts, resolve AutoInvoice and accounting exceptions, run Create Accounting to final, transfer to GL, post journals, reconcile subledger balances to GL, and close the Receivables period. The period close exceptions report highlights items preventing a clean close.
Worked example
A period will not close because three invoices remain incomplete and one receipt is unapplied. Complete the invoices so accounting can be created, apply or intentionally leave the receipt unapplied with a documented reason, run Create Accounting to final, transfer and post, then close. Reopening a closed Receivables period is possible but should be rare and controlled because GL may already be closed.
Traps
- Running an import job without first loading the file to the interface tables.
- Closing Receivables with unaccounted transactions, which breaks subledger-to-GL reconciliation.
- Confusing draft and final Create Accounting runs.
- Reopening a period after GL close without coordinating with the GL team.