(BRA) Examples: Journals generated during the electronic payment return process
Important
This content is archived and is not being updated. For the latest documentation, see Microsoft Dynamics 365 product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.
Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2
You can make electronic payments by transferring files between a legal entity and a bank. You can generate and send electronic remittance files to a bank. After the bank processes the exported files, you can import a return file from the bank. The return file contains information about the acceptance of an invoice together with the payment number that is provided by the bank, or information about the payments that are received from a customer or paid to a vendor. When you import a return file, the status of the payments is updated in the Payment status field in the Payment transfers form, based on the relationship between the bank return occurrence codes in the return file and the return occurrence codes in Microsoft Dynamics AX. For more information, see (BRA) Return occurrence codes (form). When you post the payments that the return file is imported for, only the payments that have a status of Approved are posted to a payment journal or multiple payment journals.
Approved payment lines posted to the same payment journal
You can post all approved payment lines that belong to the same journal name to a payment journal. For example, you import a return file that contains six payment lines. Of the six payment lines, three payments lines have a status of Approved, and three have a status of Rejected. Two of the approved payment lines, for journal numbers 001 and 002, belong to the same journal name, DP. The third approved payment line, for journal number 100, belongs to the journal name Test. The following table contains information about the payment lines in the return file.
Name of journal |
Journal number |
Payment line |
Status |
Amount |
---|---|---|---|---|
DP |
001 |
1 |
Received |
1000 |
DP |
001 |
2 |
Approved |
2000 |
Test |
100 |
1 |
Approved |
3000 |
Test |
100 |
2 |
Rejected |
4000 |
DP |
002 |
1 |
Approved |
5000 |
DP |
002 |
2 |
Sent |
6000 |
When you post the payment lines, the two approved payment lines for journal numbers 001 and 002 that belong to the DP journal are posted to the same payment journal, 003. However, the approved payment line for journal number 100 that belongs to the Test journal is posted to a different payment journal, 101.The following table contains information about the payment journals that are created when you post the approved payment lines.
New journal number |
From journal number |
Payment line |
Status |
Amount |
---|---|---|---|---|
003 |
001 |
2 |
Approved |
2000 |
002 |
1 |
Approved |
5000 |
|
101 |
100 |
1 |
Approved |
3000 |
Approved payment lines posted to multiple payment journals
If the transaction date that is updated for the approved payment line is different for each payment line in a return file, the payment lines are posted to different payment journals. For example, you import a return file that contains approved payment files that have three different transaction dates. The following table contains information about the three approved payment lines that have different transaction dates.
Journal number |
Payment line |
Transaction date |
Status |
Amount |
---|---|---|---|---|
001 |
1 |
January 5, 2013 |
Approved |
1000 |
2 |
January 2, 2013 |
Received |
2000 |
|
3 |
January 1, 2013 |
Approved |
3000 |
|
4 |
January 3, 2013 |
Approved |
4000 |
When you post the approved payment lines, the three payment lines are posted to three different journals. The following table contains information about the payment journals created when you post the approved payment lines.
Journal number |
Payment line |
Transaction date |
Status |
Amount |
---|---|---|---|---|
002 |
1 |
January 5, 2013 |
Approved |
1000 |
003 |
1 |
January 1, 2013 |
Approved |
3000 |
004 |
1 |
January 3, 2013 |
Approved |
4000 |
See also
(BRA) Process electronic payment remittances