Cash Receipt multiple invoices being paid by one check receiving duplicate check error
I have setup a Cash Receipts mapping and added the Apply Transaction node. I am receiving an error regarding a duplicate check number when I run the mapping. The information that I have in my data source has one check that pays many invoices. Each invoice is on a different row in the data source file. Which means the check number is a column on each row. I can see why I’m receiving the duplicate check number error, but I’m not sure how to setup the mapping to show one cash receipt that will apply to the many invoices. Can you help me please?
Answers
You’d want to make sure that your “create cash receipt” node is grouped so that it is only sent once.
I would suspect that yours isn’t grouped (because you wouldn’t need to w/o multiple apply to invoices” and so the “create cash receipt” node is called multiple times for the same document/check number. And so you get a duplicate.
But if you group in on something so that you get one record on the ‘create cash receipt’ node, it gets sent once and once cash receipt. Then do not group the apply node since you want each to be processed.
I would suspect that yours isn’t grouped (because you wouldn’t need to w/o multiple apply to invoices” and so the “create cash receipt” node is called multiple times for the same document/check number. And so you get a duplicate.
But if you group in on something so that you get one record on the ‘create cash receipt’ node, it gets sent once and once cash receipt. Then do not group the apply node since you want each to be processed.
That was very strange. I was grouping the “create cash receipt” node on the check number, but it wasn’t working. I unchecked the group by, and re-checked the box. The one thing I did change was the fact that I had 2 key fields one was a field I wasn’t using in the mapping and the other was the check number. I removed the key field that I wasn’t mapping to, and left the check number key field. Then the mapping worked as intended. Thanks for your help.
it was the multiple key fields.
99.9% of the time your “Key Fields” and “Group On” fields should be the same. If they aren’t, then the documents group differently than you expect and you end up with odd errors like this.