Going over an example wherein an invoice is transferred back and forth between 2 tenants, and what to do to in this situation.
If your company has different tenants in Nimbello, you may run into a situation where an invoice gets stuck in Tenant Transfer status and won’t process correctly. This can result in a lot of fruitless trouble-shooting, confusion, and frustration. -Three things I try to avoid whenever possible. -Let's go over an example and get this sorted out.
The Issue
When an invoice is transferred back and forth between Tenant A and Tenant B, it can end up in a loop where it gets flagged as a duplicate and auto-archived. Here's what happens:
-
Someone clicks "Tenant Transfer" to move an invoice from Tenant A to Tenant B.
- The original invoice in Tenant A moves to Tenant Transfer status.
- A new copy is created in Tenant B.
-
The invoice is then transferred back from Tenant B to Tenant A.
- The copy in Tenant B now moves to Tenant Transfer status.
- In Tenant A, the system auto-archives the invoice as a duplicate because a previous copy is still sitting in Tenant Transfer.
What Doesn't Work
🚫 Creating a new invoice – The system flags it as a duplicate due to the existing Tenant Transfer copy.
🚫 Trying to transfer the invoice again – The invoice never reaches the other tenant because it gets flagged and auto-archived as a "5-Point Duplicate"
The Fix
To resolve this:
- In Whichever tenant the invoice actually belongs, go to the Change Invoice Status page.
- Locate the invoice in Tenant Transfer status and change it to Verification.
- Click Open Edit/Save twice to push it through the workflow.
This should allow the invoice to process correctly! 🚀
Related articles:
Save Time by Auto-Archiving Duplicate Invoices