You have the option to correct in the Import Corrections form (in GL), but you lose the audit trail of what you did and why. Re-disable the segment or combination.īy making the corrections in this way you are able to keep your GL in sync with your AR activity and you have an audit trial of what you did to make the correction. Create a manual journal entry (also in GL) to move the activity from the bad account to the proper account (this is my one exception to never creating manual journal entries) andĤ. Re-run the Journal Import (in GL - be sure to include the applicable id) ģ. When you apply a receipt to an invoice it always causes an offsetting entry against the original Accounts Receivable account.Ģ. An example of this is your Accounts Receivable account that may have been valid when the invoice was originally created but it is not longer valid, and a receipt was just applied against it. Generally you have a problem if an account was valid when the activity was created, as you know, you cannot save with invalid values but, someone has since disabled either a segment or the combination. Verify that the Journal Import has a status of “SUCCESS.” If not, you had a problem that will need to be resolved or none of the items in the batch will be available for posting. Only when the Journal Import completes successfully are the Journals available for posting.ģ. If you have specified that you want the Journal Import to also run, this process verifies that the individual segments and combinations of segments are valid. Marks the records as having been passed (so they will not pass twice). General Ledger Interface:When you invoke the General Ledger Interface process, you initiate multiple programs that:įinds all of the records for the period you specified that have not yet been passed to the General Ledger ĭetermines if the debits equal the credits ![]() ![]() Verify that the amounts in the General Ledger Interface Report are reasonable and that the debits equal the credits. If anything besides headings appears, work with your IT department to resolve (since this is usually caused by a bug). If this report does run, always check each page to ensure that you have no items that could not be passed to the General Ledger. Depending on which patches you have applied, you may or may not see the Unposted Items Report. This is applicable no matter when you are running the process or if you know you will never have activity for that date, since sometimes the system uses dates other than the dates you expect.Ģ. Always run the General Ledger Interface using the starting date of the period through the last day of the period. The values used are based on the setup values for the bank where the receipts were deposited and the invoices they are paying.ġ. Whether you are manually entering your receipts or processing them through AutoLockbox, the accounting information is automatically determined by Oracle Receivables when you create and apply the receipts (not when it is still a “QuickCash” batch). If you are using Oracle Projects the account segment values are derived by a Projects’ process also called AutoAccounting and passed as values to Oracle Receivables via the Streamline process, also using AutoInvoice. ![]() You then run AutoInvoice which creates the actual transactions and uses AutoAccounting to derive the segment values for the GL Accounts. You pass the transactions to Oracle Receivables using the Receivables Interface. ![]() If you are using Oracle Order Entry (without customizations), no accounting information is available until you run AutoInvoice.
0 Comments
Leave a Reply. |