Update M3 General Ledger with Sales Ticket Information

Outcome

The general ledger in M3 is updated according to the different types of movements made in the external POS system. For example, sales, bank remittances, credit notes issuing and refunds, payment in advance issuing and refunds, tax removal refund, petty cash withdrawal.

In 'Accounts Receivable. Display' (ARS200) you can check the update of the general ledger.

New accounting objects (accounting rules, accounting events, etc.) are created and used depending on the sales ticket record type.

The various entries per record type are:

Before you start

• Meet the starting conditions listed in Defining Settings for Enabling POS Integration with M3.
• Transfer the sales ticket information from the external POS system to OPSALE (through OXSALE).
• The status of the OPSALE records is 60='Ready for finance update'.
• Define the FAM functions on 'FAM Function. Open' (CRS405/B).

  These FAM functions are used for sales tickets:

  • OP20 Sales ticket invoicing
  • OP30 Advance payments
  • OP35 Invoice payments
  • OP40 Sales ticket petty cash
  • OP50 Daily takings
• Define the accounting events on 'Accounting Event. Open' (CRS375/B).

  These accounting events are used for sales tickets:

  • OP20 Sales tickets and refunds
  • OP30 Bank remittance
  • OP35 Invoice payments
  • OP40 Petty cash expenses
  • OP50 Daily takings
• Define the accounting type 701='Petty cash expenses' on 'Accounting Type. Open' (CRS385/B).
• Define the accounting rules and accounting strings on 'Accounting Rule. Set' (CRS395/B).

Follow these steps

1. Start 'POS Sales Ticket. Update' (OPS280/E).

2. On the E panel, specify an interface round number, a facility, and a warehouse (shop).

   On the E panel, specify an interface round number, a facility, a from warehouse (shop), and a to warehouse (shop).

   The interface round number is used to identify all transactions in a batch. All records with the same round number are processed. Interface round numbers are defined in 'Number Series. Open' (CRS165).

3. Specify a transaction date.

   You can enter the transaction date manually when you enter transactions. In these instances, the current date is proposed for the transaction date by default. In 'Req/Distr Order. Open' (MMS100), a future transaction date and time are entered. This date determines when the transaction is automatically processed. The transaction date is the planned issue date. For distribution orders, the planned receipt date at the receiving warehouse is shown on (MMS100/F) to the right of the transport time.

4. Select the 'Financial interface' field. Press Enter and the general ledger in M3 is updated.

   Note: Select the 'Financial interface' field on both 'Shop. Open' (OPS500/G) and 'POS Sales Ticket. Update' (OPS280/E).

5. Specify an accounting date. The date must be within the valid range according to the FAM functions set up in 'Settings – POS' (OPS700).

6. Optionally, specify a voucher text for the transactions. The voucher text set up in (OPS700) for the division will be proposed as the default.

7. Press Enter and the general ledger is updated.

   When the general ledger is updated, the OPSALE records are set to status 80='No further update'.

Parameters to set