The functionality described in this section is designed to address certain issues often associated with a typical Shared Service operation.
The assumption is that the Shared Service operation enters, in this case, accounts payable invoices on behalf of more than one operating company. Such invoices are typically entered (i.e. registered) and costed sometimes at a later stage, sometimes at the same time as invoice entry.
This solution is designed to remove some of the more cumbersome tasks associated with invoice scanning and entry.
The benefits of this approach include:
Prior to scanning, invoices no longer need to be sorted into different piles based on the destination company
Separate AP batches no longer to be created by the user for each destination company
Scanned invoices can be processed (i.e. data entered) from a single list with Coins ERP+ automatically recognising the destination company
Reduced number of keystrokes required to enter a typical invoice.
Setup & Access
AP Parameters
Parameter | Description |
SSTTYPE | Default Transaction Type for Shared Services Invoice Batches |
The new AP parameter SSTTYPE is only consulted if Shared Service invoices are entered via the new routine called “Enter Invoices (Shared Service)”. The new routine called “Enter Invoices via Scan (Shared Service)” consults the DM parameter PLTRNSTP, in this example we have used PSCA.
AP Batch Configuration & Transaction type maintenance
AP Batch Configuration
A new batch type called PLINVSS is required. Shared Service invoices are entered automatically into this type of batch.
Ultimately, when Coins ERP+ works out which company each invoice belongs to, invoices are copied into a corresponding PLINV batch in the destination company in readiness for posting into that company’s accounts payable.
The new batch type PLINVSS is created by visiting the AP Configuration screen, pressing the “Open” button and then saving the screen (without necessarily changing any data).
Since the PLINVSS batch type is used purely as a device for grouping invoices before they are posted to their destination companies, no monetary totals are configured to be entered or controlled. The only total maintained on this batch type is the total number of transactions in the batch.
Transaction type maintenance
A new transaction type is required, in this example we have used PSCA. Shared Service invoices are entered automatically into this type of transaction.
