Period handling exceptions in reconciliation
If you post the transaction to the next Open fiscal period, the transaction date is outside the fiscal period to which the transaction is posted. This makes matching of logistic reports and financial reports more complex. You can print a report of the requests for exceptions in the Print Next-open-period Transactions (tfgld4485m000) session, and use this during reconciliation.
In the Print Reconciliation Data (tfgld4495m000) session, you can select the Print Only Backdated Transactions check box to print the reconciliation report for such transactions.
For the Invoice Accrual reconciliation group that represents the Goods Received not Invoiced (GRNI), if you print reconciliation reports with the Checklist Reconciliation Goods Received Not Invoiced (tfgld4495m200) session, the financial transaction is reported in the fiscal period of the document date instead of the posting date.
In general, backdated transactions make the reconciliation process more complex. To avoid the generation of errors when the currency differences and rounding differences are calculated, logging antedated transactions with a transaction date earlier than the most recent archiving date of the reconciliation data is not permitted for the following reconciliation areas:
- Inventory.
- Consignment Inventory.
- Assembly Line WIP.
Example
If you received goods late on January 31 and you register the receipt on February 1 but with a transaction date of January 31, the following situation occurs. The posting date and the document date differ.
| Fiscal period 101/01 – 01/31 | Fiscal period 202/01 – 02/28 | |
| Operations Management transaction | Receipt: Transaction date = 01/30 Document date = 01/30 | |
| Financial transaction | Receipt: Posting date = 02/01 Backdated: Document date = 01/30 |