Direct electronic sales invoicing

Electronic invoice solutions must include vendor to customer inbox with functionality to upload a copy of the e-invoices to a government portal. Both parties must use the same software or standard format to exchange electronic messages. Alternatively, a third-party service provide can be used, or the vendor can send the e-invoice to the customer using a government or tax authority portal.

Reliable audit trails for paper and electronic invoices are required for authenticity of origin, integrity of content, and legibility of invoices.

Australia specifics

The Australian and New Zealand governments have agreed to a common trans-Tasman electronic invoicing standard (PEPPOL). PEPPOL is the standard for universal digital exchange of invoices between suppliers’ and purchasers’ accounting systems.

PEPPOL e-invoicing is required for all government departments and agencies as of June 2021. State and local governments are required to use it by June 2022. Suppliers who issue e-invoices using the PEPPOL framework will be paid within 5 days. The adoption of electronic invoicing is required by July 1, 2022 for all Commonwealth government agencies.

How Infor meets this requirement

Clients can create billing invoices using customer orders or direct billing invoices. Localization integration only works if the invoices are created with line items in FSM.

When you release the billing invoice, successful batch jobs must be run to process them into the subsystem update. The invoice is moved to Receivables. The successful triggering of the FSM_ION_SyncInvoice_Outbound BOD results in these outcomes:
  • The corresponding invoice record in Localization Services Platform (LSP) is created.
  • The status of the invoice is Unreleased.
  • A Waiting for PrcoessInvoice BOD message is displayed.
The details of the invoice cannot be changed. The FSM_ION_ProcessInvoice_Inbound BOD is received from LSP and the statuses are displayed in the BOD, such as Forwarded, Failed, Rejected, Sent, or System Error.

This list shows the scenarios that are included:

  • Direct Billing Invoice - Invoice Type
  • Direct Billing Invoice - Credit Memo
  • Customer Order (CO) based Invoice - Invoice
  • Customer Order (CO) Return

The Receivable Invoice - Invoice and Credit Note scenario is not included.

Use this Localization Services Platform (LSP) setup to test this requirement:
Field Values
Default E-invoice Type PEPPOL Access Point
Tax Code Translation 10%TAXINV
Payment Method Translation CHK

The PEPPOL invoice format is supported. Australia - Electronic Sales Invoicing subscription is a requirement. To set up LSP for integration, you must set up AE and PEPPOL registration and Gateway Connectivity. You must also specify default codes, contact masters, tax codes, and payment methods.

See the Infor Localization Services Platform User Guide.

See e-Invoicing requirement.