Check Printing Set up in Oracle Fusion

Well, If you work on any Oracle Cloud finance project, Check ( Cheque if you speak queen’s English) Printing will be one of the most crucial tasks in the project. If you have developed any report, check printing is more of a simple minded job which requires more efforts in alignment of the fields. Except one tricky part: Overflow. To handle the overflow condition either you can take the route of code or you can do check printing set up in the system.

So what is overflow? If you have ever received a refund from a company or had been paid by one, chances are that you would have received a check with remittance ( why are they paying you) info on it. If you had observed, this check is not of the size of regular checks which we get in check books. Rather it is a special paper with bottom part containing the regular check and upper part having remittance info. Now consider a scenario where a check is issued to a vendor to pay multiple invoices. Of course, this page has a finite length and can contain only so many of invoice information in top section. If the number of invoices exceed the limit, we will need another check to print the remittance info. In this case first check must be marked as VOID ( so that it is not misused by anyone) and subsequent check will be used to make a payment.

So what is the tricky part: Since check ( portion of the paper which will be sent to bank for payment) has a predefined position on the paper, number of invoices must not shift it up or down. And in case of overflow, we must mark the check as VOID pragmatically.

Since you will be developing an RTF template, following posts can be helpful:
RTF- Looping Finite Number Of Times
RTF Number Formatting With Examples
RTF Date Formatting With Example

Options available:

1. Find out with hit and trial the number of lines your check can take. Obviously it will depend on the font you choose to print the invoice info along with layout of the check which will differ bank to bank. Then keep counting the lines till you reach the threshold and mark the check void. Continue on next page.Keep repeating the steps till you reach the check which can be printed as normal check.
2. Set up your system to mark the checks void when limit is reached.

Lets discuss the second option because first method anyway is more of dumb work.

Check Printing Set up:

1. Find out how many lines can the check take.
2. Now every check will correspond to the account which will be used to pay the money. This account needs to be edited for number of lines you want to print on a check. Navigation is
   1. Go to Set Up and Maintenance. Query the task “Manage Bank Accounts”. Query the bank account which will be used for payments. Scroll down to bottom. Open the document which you want to control ( Unless set up was done by a creative person, it’s name must have word “Check” in it).
   2. Now set the field “Number of Lines per Remittance Stub” to number of lines you want to print on the check. 

So what does this set up do? If this value is not set, Oracle will try to print all the invoices on same check ( remember Oracle does not know how long your check paper is!!). Check screenshot below. Oracle tried to print all 4 invoices on same check. ( Yes, I chose only 4 invoices to be paid)

But once this option is set up, same payment will be broken in multiple checks. Only one of the check in payment will not be void. Since I set the value to 3, my first payment will have 3 invoices but they will be marked as overflow while second payment will have 1 invoice and will have the amount same as sum of all the 4 invoices.

So Oracle split the payment into 2. Using the status of the payment, we can programmatically mark it as void. No need to keep a counter to see if check has to be marked VOID.

This payment has 1 invoice and amount same as sum of all 4 invoices.

So it brings us to our second question: how to pin down the check at the bottom of the page at designated place. After all, our check data should not shift up or down based on the lines in remittance information. So here is the simple trick:

Create 2 tables one above another. Upper table will be used for remittance info. Lower one will be used to print the check properly. Now select upper table –> right click –> Row Tab –> Check “Specify Height” checkbox. Fill the height (You will have to see how many lines do you want your upper table to have. This obviously will depend on the font and size you choose). Make “Row Height Is:” option as “Exactly”. Now format your lower table for your requirements. As height of lower table will always remain same for check of a particular bank. so you dont have to do trial and error here. But fix the height of this table too. and you are all set with your template. Upload it in Oracle Fusion Instance and if other set ups are fine, your checks will print as expected. And one more thing, borders of both the tables unless really required.

Happy check printing. Hopefully your client, vendors and bank will be happy. If any question, do let me know. Who knows I might have stumbled on that problem already.

Disclaimer: This method has been tested till release 13 of Fusion finance. Though I don’t see it failing unless Oracle changes the payment XML structure it generates.

Related posts:
Check Printing Set Up in Oracle Fusion
How To Fetch (Query) The Payment Details In Fusion
Payment Process Request Query in Fusion
RTF- Looping Finite Number Of Times
RTF Number Formatting With Examples
RTF Date Formatting With Example

By the way, Here ( India) or Here ( Other Geographies) are few UNCONVENTIONAL tricks which I have learnt to improve the performance of BI reports or SQL queries. Try them only when nothing else works.. kind of SOS...

Feedback:
Hope the article helped you. If it did, please rate the post. In case it didn’t, do leave a comment to let us know what did we miss.

Reference:
support.oracle.com