FCX highly recommends you require your Vendors to follow this rule when emailing you their Invoices:
1 Email = 1 Attachment = 1 Invoice = 1 BP
BUT, we recognize that it can take time to arrange that after you start using FCX AP, and even after, mistakes can happen.
IF the vendor happens to attach 2 Invoice Documents to their email, FCX can usually automatically separate the bill into 2 separate VIM Invoice cards.
BUT if the vendor bundles multiple Invoice Documents in a single file, you need to take extra steps to separate them out in FCX.
We recommend the below process to handle this later situation.
Note that these steps make sense where each bill in the bundle has its own Invoice #. Under other circumstances we'd recommend a different process.
To handle this:
- FCX captures the initial email and creates 1 VIM Invoice
- You download a copy of the bill Document to your local computer. From the VIM Review dashboard, click the Download icon in the upper-right corner, above the document preview.
- You process the existing, captured Invoice as the first Bill included in the bundle: You ignore the extra pages in the document after the first Bill.
- You manually create a VIM Invoice card for each of the other Bills in the bundle:
- If you're in Web, make sure the Desktop Integration button it toggled-on in the lower-left corner of the dashboard list
- Open the VIM Inv list drawer on the left side of the dashboard and click the + next to the search box on top:
- Open your local copy of the Bill Document to use while filling-out the VIM Inv card
- Upload a copy of the Bill Document from your local computer as a Related Document so it can be easily viewed later by Approvers:
- Note after you save the created VIM Inv, there's an extra step to take. On the VIM Inv card ribbon home tab, in the Actions group, click "Submit" to change the Stage from "Draft" to "Pending." After this, you can Validate and Send the Inv for Approval like normal:
- Repeat for each additional Bill in the Bundle.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article