/
Invoices with foreign currency - requirements analysis
Invoices with foreign currency - requirements analysis
This page describes requirements related to foreign currencies in orders and invoices app.
Requirements Analysis
Description
A user creates a PO and POL, the price is recorded in a foreign crrency. The following errors occur when the user processes the invoice for this PO/POL:
Scenario 1: Invoice will be processed in primary currency (= system currency = e.g. EUR)
- User creates POL and enters the amount/price in a foreign currency
- The system calculates the encumbered amount in the primary (=system) currency - this will be displayed as encumbrance in the finance app as transaction
The user creates an invioce and invoice line for the POL - when linking the POL, the system displays the original amount in foreign currency but displays it as amount in primary currency - only a EUR sign is attached to the original price in foreign currency and thus further calculated- The correct amount from encumbrances (finance app) is not used
- The further calculation is therefore based on the original price - just with primary currency → The correct amount from the encumbrance is not used
- The payment is therefore incorrect
Scenario 2: Invoice Processed in Foreign Currency (e.g. GBP)
- After creating the invoice line, the amounts from the purchase order line are correctly adopted, meaning the correct encumbered amount from the finance app is used.
- However, additional costs cannot be processed in the primary currency (EUR).
- This includes VAT, shipping costs, etc.
- Currency differences cannot be compensated in the primary currency (as additional costs or similar).
- Although it is possible to update the invoice amount by adjusting the exchange rate, which typically must be calculated first, this is very cumbersome in practice.
General Problem
- The invoice shows either the primary or the foreign currency price.
- It is essential to see both prices, especially for statistical surveys regarding price development and trends.
Required Fields and Functions
Scenario 1:
- During invoice processing, the encumbered amount from the purchase order should be used for further calculations.
Scenario 2:
- When adding additional costs, it should be possible to select a currency or at least use the set primary currency.
General:
- More transparent display of the original price (foreign currency) and the actual invoice price – possibly an additional field for the original price.
- When selecting the status "Checked" in invoice app:
- Output of actual amounts (additionally in the primary system currency).
- The invoice amount then has the status "intended for payment" in the budget overview of the finance app.
- Advantage: all data of the invoice can still be changed.
- Alternatively: new additional action: Review - as a function before approving and paying.
- Output of actual amounts (total price and additional costs) on the invoice, invoice lines, on the purchase order for linked invoices.
- Option to specify amounts in both foreign and primary currency – the system should then calculate the exchange rate.
- List price (in the original currency) as a separate field on invoice lines – added value for reports, especially for Scenario 1.
Tasks
- ...
Additional Information
- ...
Relevant Functional Analyses
Discussion in a D-SIG
Relevant existing Jira Tickets
- ...
, multiple selections available,
Related content
Spike: Avoiding partially paid invoices POC
Spike: Avoiding partially paid invoices POC
More like this
Examples: Foreign currency
Examples: Foreign currency
More like this
Create invoices by importing MARC Bibliographic Records
Create invoices by importing MARC Bibliographic Records
More like this
Add alternate sources for currency exchange rates
Add alternate sources for currency exchange rates
More like this
Create invoice automatically from purchase order
Create invoice automatically from purchase order
More like this
Integration with external financial systems
Integration with external financial systems
More like this