1.In R12 Oracle Payables we have 3-tier hierarchical Invoice architecture
a.Header
b.Line
c.Distribution.
2.In R12 Oracle Payable Invoice line is now a Child of Invoice header and parent of invoice distribution entity.
3.Three different ways are available to enter an invoice from the Invoice workbench
a.Invoice header to Invoice Lines and then to Invoice Distributions.
b.Invoice as matched to a Purchase Order or Receipt, they will need to
manually look for and pick the matched records from searching result.
c.Quick match to have the matched data automatically fetched from PO or
Receipt, and then populated into the invoice.
4.The Invoice distribution entity will now exist as the child of the Invoice line entity. When the invoice lines are created, the distribution data are automatically generated and tied to the lines.
5.Another new feature is multi-period accounting entry , with this mechanism used cab create deferred accounting data for future data.
6.Now Oracle Payables enables invoice approval at both header and line levels.
7.The invoice corrections can be made with various types, including price corrections, quantity corrections and amount corrections, at invoice line level.
8.With invoice lines implementations, freight charge can be easily allocated to the real item lines on item.
9.User can apply the available prepayment onto the current invoices during the creation of standard invoices. Pre-Payment will be created a separate line in the Invoice and Gross amount of the invoice will be automatically reduced based on the Pre-payment amount.
10.During Invoice Validation process Oracle Payable validation process will check for validation of the various rules (set of invoices) , and of there is any violation of the tolerances rules then the invoice will be put on hold.
a.Header
b.Line
c.Distribution.
2.In R12 Oracle Payable Invoice line is now a Child of Invoice header and parent of invoice distribution entity.
3.Three different ways are available to enter an invoice from the Invoice workbench
a.Invoice header to Invoice Lines and then to Invoice Distributions.
b.Invoice as matched to a Purchase Order or Receipt, they will need to
manually look for and pick the matched records from searching result.
c.Quick match to have the matched data automatically fetched from PO or
Receipt, and then populated into the invoice.
4.The Invoice distribution entity will now exist as the child of the Invoice line entity. When the invoice lines are created, the distribution data are automatically generated and tied to the lines.
5.Another new feature is multi-period accounting entry , with this mechanism used cab create deferred accounting data for future data.
6.Now Oracle Payables enables invoice approval at both header and line levels.
7.The invoice corrections can be made with various types, including price corrections, quantity corrections and amount corrections, at invoice line level.
8.With invoice lines implementations, freight charge can be easily allocated to the real item lines on item.
9.User can apply the available prepayment onto the current invoices during the creation of standard invoices. Pre-Payment will be created a separate line in the Invoice and Gross amount of the invoice will be automatically reduced based on the Pre-payment amount.
10.During Invoice Validation process Oracle Payable validation process will check for validation of the various rules (set of invoices) , and of there is any violation of the tolerances rules then the invoice will be put on hold.
