Once you have created and frozen the payment batch, you can print the cheques and generate BACS payments.
Before doing this, check that the invoices show as Selected for Payment in Purchase Ledger > Payments > Select/Deselect Invoices (Manual), and the that batch has a status of Frozen in Purchase Ledger > Payments > Payment Batches.
If you print BACS remittances separately from processing the BACS payments, you must print the remittances after you have processed the payments.
To process BACS payments:
Go to Create BACS.
Create BACS – Select Batch
In the Batch Number column, click the link for the batch that contains the payments you want to process.
Select a configurable cheque document. (You need to do this even though you are not printing cheques.)
The Main tab shows you the number of items in the BACS payment
On the BACS Processing tab:
Select the bank account from which the payments will be made.
Verify the date to appear in the BACS file; this defaults to today’s date.
Create the BACS
Select any Output Options.
Click Next (
).Coins ERP+ displays a message informing you of the number of cheques and/or BACS payments that will be included in the payment run. To continue, click OK. Otherwise, click Cancel to return to the selection fields.
Depending on the output options you selected, Coins ERP+ either displays a "Task completed successfully" message to tell you that the print request has been sent, or displays a "Generating" page, and then displays the printable output PDF file).
Next, print the BACS remittances; use Print BACS Remittances.
You can print a Payment List to check that the payments are correct (use Payment List).
Finally, you need to post the batch.
BACS Payments – Parameters
PL/BACSFILE
BACS File (Full Path Name)
The full path and file name for the BACS details file.
The file name can contain tokens in square brackets that will be replaced when creating the file. This is necessary if you are creating more that one file in a run.
The tokens that can be used are:
[SECTOR] Sector based ledgers only. Replaced with the sector code.
[IBANBANK] UK use only. When creating separate files per bank being paid from, this will be replaced with the IBAN code for the bank.
[SPLIT] Intended for UAE and the production of WPS. This will be replaced with the sponsor employer ID.
[DATE=YYYYMMDD] Replaced with the creation date in the format specified.
[TIME=HHMMSS] or [TIME=HHMM] Replaced with the creation time in the format specified.
[BANK] Replaced with the bank code.
[KCO] Replaced with the number of the logged-in company.
[USER] Replaced with the user ID of the current user.
[PAYTYPE] Replaced with the specific token added to the Document Designer form selected when creating the BACS file. This can only be used for PL and SC BACS files.
PL/BACSFUTR
Number of days that BACS payments can be dated in the future
The maximum number of days in the future that the Purchase Ledger BACS processing date can be set to. If blank, the default used is 14 days.
Note this parameter does not apply to US companies (where SC/TAXRULES = US).
PL/BACSMED
Format for BACS Output File
The medium for BACS files.
The options are:
1 = 5¼" floppy disk
4 = Datacom
5 = BACSbox. The BACS file generated with media 5 will contain an optional ID field (account/employee number) if the CO parameter BACS-REF is set to Y. This ID is appended at the end of the line.
6 = ANZ Direct Credits format
7 = Bank of Ireland format
8 = Australian format
9 = Configurable format. This is configured using the CB parameter BANKORD.
10 = HSBC Hexagon format
11 = HSBC Hexagon format (alternative)
12 = Allied Irish Bank format
14 = National Bank of New Zealand Direct Link Domestic File Transfer
16 = USA format.
17 = Bank of America Paymode format (in purchase ledger and Subcontract Ledger modules); not used in Payroll module.
19 = Canada.
code = The code of a file format configured using BACS File Definition.
BACSMED can have a second entry, which is text that will be put in to the BACS application field (a field that appears in the header identifying the application used to generate the file). By default COINS puts the module code. If the CO parameter BACSAPPL is set to Y, COINS appends the COINS company number in the application field.
For media type 6, if this is set (that is, a second value is supplied to the BACSMED parameter), then this value is placed in the header record for this type, field 8 of the ANZ spec "Description of Entries on File". The ANZ bank software uses this value, in conjunction with the BACSUSER parameter (id value), to determine the parameter to use when selecting the template for the load.
BACS User Id
A comma-separated list of your company's BACS User ID and BACS User name as supplied by the financial institution.
These must appear in the order "<id>,<name>".