1 | No inter‑company transactions at all when base currencies differ
Whenever I try to create any document that involves two companies whose base currencies are different—
- an Payment of an AP Bill on behalf of another company with different base currency
- an inter‑company GL journal entry
- a Cash Transfer between branches
—the system blocks the save with the message that “branches has different base currency”
Question: Is there a supported way to post any inter‑company document when base currencies differ, or am I missing a configuration flag / workaround?
2 | Vendor / Customer sharing across base currencies
I’ve noticed that Intercompany ▶ Extend as Vendor/Customer creates a single vendor (or customer) record that remains usable by all companies—even when those companies’ base currencies differ.
By contrast, a standard vendor or customer is limited by the “Restrict Visibility To” rule, which forces us to segregate records by base‑currency groups.
Question: Why can’t the same cross‑base‑currency logic used by Extend as Vendor/Customer be applied to ordinary vendor/customer records as well?
Allowing a single vendor/customer master to serve every company would prevent the need to duplicate the same supplier across multiple base‑currency groups.Is this limitation driven by technical constraints or accounting policy? Any roadmap insight—or practical work‑arounds—would be greatly appreciated
3 | Purchase Requisitions feature disappears
The moment I enable Multiple Base Currencies, the Purchase Requisitions feature is forcibly disabled.
Question: Is there an alternative workflow (e.g., using Purchase Requests only, or another module) that Acumatica expects us to adopt in multi‑base environments, or is requisitioning simply unavailable once Multiple Base Currencies is on?
