Check Remittance Forms absent in Business Central - until now
We were spoiled coming from GP, which had check remittance forms for invoice overflow from the check stub. In Business Central, invoice overflow on the check stub gets printed on the next check stub, with VOID stamped across the second check face. It's not pretty and throws the customer's check numbering off.
PDG Consultants was asked to customize Business Central, to create a check remittance report (as in GP) - because our customer's AP Clerk of 20 years threatened to quit, unless we did it.
Here are a bunch of screenshots showing that extension.
22 invoices were added to a vendor in our client's sandbox. Our remittance customization has a limit of 20 invoices, so we will write a check to apply 20 of the 22 open invoices. The Payment Journal below gets the amount filled in once all the invoices have been chosen to apply.
Here are the invoices to Apply, with 20 selected to pay.
Here is the Check Option Window ready to print the check.
Here is the check, with 10 invoices on the stub and a note on the stub "*** CONTINUED ON REMITTANCE ***".
This client used pre-printed check stock, so no need to show the customer origin data: address, bank, MICR, captions, etc.
We try to Post the check after printing, but the system prevents us from Posting until a Remittance is printed.
There is now a button on the Payment Journal, under the Process Menu to "Print Check Remittance".
A customized Word report was created to display/print the Remittance form.
Here is the Customized Check Remittance for Business Central showing all invoices which had been applied, not just the remainder from the stub.
Verifying these 20 invoices were paid was easily done by visiting the Vendor Ledger History.
Our client has been using it for a year now. Haven't heard any complaints. Perhaps we'll put it on App Source, after we extend the maximum applied invoices well beyond 20.
Special thanks to my genius Partner, Ranjith, for writing this extension for Business Central.
Steve Simon
PDG Consultants, Inc.
Comments