Note: Search for the word 'Mastercard' in Unipedia to find all articles about Mastercard Leverandørservice and Betalingsservice.
There are four articles you should read to get started with these charging solutions.
- Collection solutions (Direct Debit)
- Setup (Mastercard)
- Mandates (Mastercard)
- Payment suggestions (Mastercard) (this article)
There are a few differences between LeverandørService and BetalingsService. Where it only applies to one of the two services, it will then describe which service it is.
It is possible to make collections and payments. In the description, the word Payments will cover both types.
Payment types (Supplierservice and direct debit)
- Collection, which means that you charge your receivable to your customer's account.
- Payment, which means that you transfer money to your customer's account. For example, a credit note.
In this screen, payments are made.
Note: All open debtor entries are displayed
Here is an overview of the columns.
| Column |
Read/Write |
Description column |
Note |
| Payment status |
R |
Payment status |
The payment status will automatically be updated, but can also be changed manually.
A more detailed description can be found in the section 'Button - Change status'. |
| Date sent |
R |
Sent is the date/time when the invoice was sent. |
|
| Account |
R |
Debtor number |
|
| Account name |
R |
Debtor name |
|
| Date |
R |
Posting date of the entry |
|
| Due date |
R |
Date when the payment is due |
|
| Payment date |
W |
Payment date |
The payment date is initiated with the Due date and if this is exceeded, the payment date is filled in with Today's date. Bank holidays will be taken into account if this feature is enabled. Read more here.
The payment date is the business day when the amount is posted to your and your customer's accounts. |
| Text |
R |
Posting text |
This text is not output in the payment file. |
| Invoice |
R |
Invoice number |
Supplier service:
Only invoices with invoice lines can be chargedPayment service:
Only transactions with an invoice number can be charged Note: If the parameter 'Allow transactions without invoice number' is activated, it will be possible to charge/pay transactions without an invoice number |
| Amount |
R |
The posting amount |
Amount that will be charged when Principle = Default |
| Remaining |
R |
Remaining amount |
Amount that will be charged when Principle = Remaining |
| Partial payment |
W |
Partial payment amount |
Only to be filled in if you do not want to charge the full amount.
Will automatically be filled in if the amount received differs from the amount charged.
Betalingsservice: No amount can be deposited. |
| Account assignment type |
R |
Account assignment type |
|
| Status information |
R |
Status information |
A chronological log of all activities performed for the current record |
| Commentary |
W |
Internal comment |
Information in this field is for internal use only and will not be printed in the payment file |
| System info |
R |
System information |
In this column, information that is relevant to the individual entry is entered. This can be error messages etc. |
| Payment format |
W |
Format (File formats for payment methods) |
An indication of which payment method is selected for each payment. |
| Appendix |
R |
Annex number |
|
| Payment |
R |
Payment terms and conditions |
|
| Currency |
R |
Currency code |
LS and BS only allow payments in DKK |
| Payment instructions code |
R |
FIK71 Payment ID |
Payment ID used on the Payment card. Only filled in if activated under parameters otherwise Betalingsservice will autogenerate a unique Payment ID |
| Payment reference |
R |
A unique ID for the payment |
A unique ID is generated for the payment when it is sent to Mastercard. |
| Collective payments |
R |
An Id for collective payments |
Collective payments use the ID for grouping |
| Allow overwriting |
W |
Validation |
Only one amount can be charged per debtor per payment date. If you want to overwrite a charge, you must allow overwriting |
| Have invoice |
R |
Invoice exists |
Invoice entry exists in the invoice journal |
| From creditor |
R |
Creditor/Debtor entry |
Marking where the entry comes from |
Here is an overview of the buttons in the menu
Controllers
When you press this button, the system will run through a series of validations for the individual entries associated with the current Payment Format. For example, the system checks for submission deadlines or whether there is an active mandate and a number of other validations. The result can be seen in the 'System info' column. Only payments that have 'Ok' will be sent to Mastercard.
Exporting
All selected payments where status is <Blank> will be sent to Mastercard. A validation is automatically performed before sending. Read more about Data exchange with Mastercard further down in the description.
Betalingsservice
When sending direct debits to Betalingsservice you will get the dialog box below. If you have many invoices, it will take a relatively long time to create the invoice file. It will therefore take some time before the status changes to Sent. The Export button will therefore be disabled to prevent multiple clicks.
Delivery deadline (Deliveryear service)
Mastercard has the following delivery deadlines.
The delivery deadline for direct debits is 1 banking day before the payment date at 16.00 (Uniconta at 15.00)
The delivery deadline for payments is 2 banking days before 16.00 (Uniconta at 15.00)
The recommendation is to send payments as early in the day as possible. Especially in cases where payments are sent with a payment date of the next business day.
Sending your data in good time allows you to correct any errors and send a new delivery within the deadline.
| Payments can be sent |
Note |
| every day |
The payment day must be a banking day |
| Up to 90 calendar days ahead of time |
Payment date must be a business day |
| but only one charge or one payment |
This applies per customer number per payment day. |
Betalingsservice - Total solution vs. Basic solution
If you have chosen the Basic solution at Mastercard, a direct debit can only be sent to customers who are registered for Betalingsservice. The customer must have a mandate in Uniconta with the status 'Enrolled'.
If you have chosen the Total solution, Mastercard will ensure that the charge is sent to the debtor regardless of whether there is a mandate or not.
Submission deadline (direct debit)
The submission deadline for direct debits is the 6th last banking day of the month before the payment month. The payment date can be up to 90 days in the future.
It is recommended that you send your data in good time, as this allows you to correct any errors and send a new delivery within the deadline.
| Payments can be sent |
Note |
| every day until the 6th last banking day of the month before the payment month
Before 18:30 (Uniconta before 17:30) |
The payment day must be a banking day |
| Extension - every day until the 3rd last banking day of the month before the payment month
Before 18.3o (Uniconta before 17.30) |
For an additional fee to Mastercard, the delivery deadline can be extended. Read more here. |
| Up to 90 calendar days ahead of time |
Payment date must be a business day |
| but only one charge or one payment |
This applies per customer number per payment day. |
It is recommended to check the Betalingsservice Customer Portal regularly, as not all errors are reported back to Uniconta.
Example of errors that are not reported to Uniconta. If you have a Basis solution and send charges to customers with a MandatID that is not known to Mastercard, Uniconta will not be notified, but the error will be visible in the Customer Portal and you will also be informed via your e-boks.
Stop payments
A sent collection file cannot be stopped from Uniconta once it has been sent.
If you have been sent incorrect collections, you must contact Mastercard as soon as possible, as they have the ability to stop the file.
Mastercard will charge a fee if the file has already been forwarded in their system. If an error is not discovered until the day after the file has been sent to Mastercard, Mastercard can only stop charges to customers who are registered for Betalingsservice.
In Uniconta, you can change Status = 'Sent' to Status = 'None' and then resend the invoices. You have to be very careful here, as a customer may risk being charged twice.
Import
Uniconta will search for files from Mastercard and load them.
Note: Search must be pressed before files can be loaded. Filtering is not allowed.
Read more about Data exchange with Mastercard further down in the description.
Mandates
Information about mandates that have been activated or deactivated will be updated in Uniconta.
The payment method is automatically updated on the Debtor when the mandate becomes active.
Payments
All incoming payments will be transferred to an accounting journal.
There may be situations where the system cannot find the invoice to offset against. This may be because the invoice has been offset against another payment. In these situations, you will always be able to find the payment in the accounting journal and then handle it manually.
There may also be situations where the payment deviates from the original invoice amount. The deviating payments will not be posted automatically, but will be in the accounting journal and can then be handled manually. The deviating amount will be entered in the 'Partial payment' column.
It is recommended to check the Status information in the file archive. Any errors will be specified here. Read more about this in the File archive section.
The following only applies to Betalingsservice
When the 602-file is loaded, the payments are automatically transferred to an Accounting journal. In the text column, a number of codes are used, as described below.
(!) Means that there is a transaction to pay attention to here, as it deviates from the norm.
(!) M:<nnnnn > M is an abbreviation of Mandate. This code is used if there is no matching Mandate in Uniconta. The Account column can therefore not be filled in.
(!) Unsubscribed (0238) The collection has been unsubscribed/rejected before the due date, therefore no amount has been deposited in the bank (amount column = 0)
(!) Unsubscribed (0237) The collection has been rejected before the due date, therefore no amount has been deposited in the bank (amount column = 0)
(!) Unsubscribed (0237) The charge has been rejected after the due date but before the 7th of the month (payment rejection deadline). The amount must therefore be credited to the bank.
(!) Unsubscribed (0239) The bank has rejected the charge. The amount must therefore be credited to the bank.
(!) If the transaction only has this flag, it's because the system can't find the invoice to settle with.
Collective payments
It is possible to collect payments with the same payment date. There is a longer description of the feature further down in the text.
Change of status
The payment status will automatically be updated, but can also be changed manually. In the table below is a description of the different status outcomes. It is possible to change the status of an entry, but there are some limitations - these are described in the last four columns.
| Status |
Description |
Change -> <Blank> |
Change -> Resend |
Change -> Waiting |
Change -> Stop |
| <Blank> |
Default status where the line is awaiting an action. All lines can be changed to this status regardless of the status of the line. However, this will not always be appropriate. |
No, you can't. |
No, you can't. |
Yes, you can |
No, you can't. |
| Sent |
The payment has been sent to Mastercard.
A receipt file is then awaited from Mastercard. |
Yes, you can |
No, you can't. |
No, you can't. |
Yes, you can |
| To be treated |
The payment has been received by Mastercard and the receipt file has been loaded.
The payment will now be processed by Mastercard. |
Yes, you can |
No, you can't. |
No, you can't. |
No, you can't. |
| Unsubscribed |
The payment has been sent to an agreement that has been deregistered with Mastercard. |
Yes, you can |
Yes, you can |
Yes, you can |
No, you can't. |
| Rejected |
The payment has been rejected by the debtor. |
Yes, you can |
Yes, you can |
Yes, you can |
No, you can't. |
| Reversed |
The payment has been reversed. The debtor has had their bank reverse the transfer. |
Yes, you can |
Yes, you can |
Yes, you can |
No, you can't. |
| Errors |
There are one or more errors that Mastercard has registered via an error code. The error description is in the Payment status column |
Yes, you can |
Yes, you can |
Yes, you can |
No, you can't. |
| Received |
The payment is complete |
Yes, you can |
No, you can't. |
No, you can't. |
No, you can't. |
| Difference |
The payment has been completed - but there is a discrepancy in the amount charged compared to the amount paid. The amount will appear in the Partial payment column |
Yes, you can |
No, you can't. |
No, you can't. |
No, you can't. |
| Transmitting |
This payment status can be set manually if you want to resend |
Yes, you can |
No, you can't. |
Yes, you can |
No, you can't. |
| Waiting |
This payment status can be set manually |
Yes, you can |
No, you can't. |
No, you can't. |
No, you can't. |
| Information |
Important information |
Yes, you can |
Yes, you can |
Yes, you can |
No, you can't. |
| Stop |
This payment status can be set manually. See further description below. |
Yes, you can |
No, you can't. |
Yes, you can |
No, you can't. |
Only applies to Betalingsservice: In Uniconta you can change Status = 'Sent' to Status = 'None' and then resend the collections. You must be very careful here, as a customer may risk being charged twice.
Status 'Stop' (Supplier Service)
It is not possible to stop or delete an entire delivery.
Instead, you can stop/cancel one or more payments by submitting one or more new payments with DKK 0 as the amount and the same payment date as the payment(s) to be canceled. By changing the status to 'Stop', Uniconta will make sure to send the cancellation.
In this way, the customer is not charged an amount. However, you should be aware that some banks will show the €0.00 transaction on the account overview, depending on your customer's bank.
Note: Last loaded and updated payment to the same customer with the same payment date will cancel previously updated payments.
This applies regardless of whether you deliver the payments in the same or multiple deliveries.
When you receive receipt and note information, it will show that the amount has been replaced by a new payment.
Transferto draft
Uniconta will automatically transfer the charges to the accounting journal when files are received from Mastercard.
It is possible to transfer entries manually with this feature.
The function will transfer the selected entries to an accounting journal. You will be presented with the dialog below.
The dialog will be filled with the default values you have specified under 'File formats for payment methods'. In the example above, the charges will be transferred to the 'Day' draft and posted to the bank account 5850.
Searching for payments
Payments can be selected by Due date by using the date delimitation below.
You can use the various filtering options available in Uniconta. Here you can filter the Payment Status and Account columns.
Note: Only the payments that are searched for will be output in the payment file.
Note: Via Layout/Other fields you can retrieve fields from the Mandate table. Mandate ID and Mandate status are inserted below. You can then filter on active mandates.
Note: You can use the Comment field to search for payments.
In the example below, a code 'x' has been entered in the payments to be printed. This makes it easy to filter on them.
Status 'Pending'
The 'Pending' status can also be used to search for payments. Use the 'Change status' button to change the status of the selected payments. Payments with status 'Pending' will not be included in the payment run.
View status information
The status information can be read directly in the column, but for a better overview it can be displayed at the bottom of the screen.
Invoice text
This is only used for Betalingsservice. Here you can see the texts for the debtor's Payment overview. Read more about setting up the Payment overview
here.
Collective payments
Collect payments allows you to collect payments per debtor per payment date. This can be an administrative and cost-saving feature if you have multiple collections for the same debtor.
For Leverandørsservice and Betalingsservice, only one payment per debtor per day is allowed, but by using Samlebetalinger you can collect multiple payments with the same payment date.
Collective payments are activated by pressing the 'Collective payment' button. Uniconta will now try to collect the payments according to the previously described conditions. It is recommended to filter out all the payments you do not wish to pay at this time. This can be done by entering a due date or using some of the other filters in Uniconta.
All payments will be checked before merging and any incorrect payments will be placed in the 'Deselected' group - read more about the 'Deselected' group below.
Collective payments can be canceled by pressing the button again.
Credit note or similar.
Credit notes or other transactions with the opposite sign are also included in collective payments.
Betalingsservice: Only transactions that have an underlying invoice can be collected.
Button 'Unfoldall'
This button becomes active if you use collective payments. All groups will be unfolded by pressing this button.
'Collapseall'
button
This button becomes active if you use collective payments. All groups will be collapsed by pressing this button.
The button - 'Check'
will check each payment in the group and should one of the payments be incorrect, it will not be included in the total payment. The error description can be found in the 'System Info' column.
The payments in the example above have been grouped into four groups.
The first three groups will result in six charges. The last group 'Deselected' contains all the payments that will not be output in the payment file.
Below is a description of the groups. Groups are grouped according to a Collective Payment ID, which is a combination of the unique key (<Debtor number>-<Payment date>) that characterizes the individual payments in the group.
Collective payment: -
The payments in this group will be handled individually. This means that four collections will be created for the four debtors.
Collective payment: 100100-20180713
Debtor 100100 has six collections with the payment date 13.07.2018. A collection of DKK 29,715.00 will be created. The payment will be executed on d. 13.07.2018.
Collective payment: 100106-20180713
Debtor 100106 has two invoices with the payment date 13.07.2018. A collection of DKK 2,000.00 will be created. The payment will be executed on d. 13.07.2018.
Collective payment: Deselected
All payments that are incorrect or otherwise do not meet the selection requirements are placed in the 'Deselected' group. These payments will not be output in the payment file.
TransfertoAccountingjournal
Uniconta keeps track of which payment lines have been collected when transferring to Accounting journal.
In the example, 6 lines are transferred to the accounting journal. The invoice numbers related to payment are listed in the 'Offsets' column and will automatically offset the invoices when posting.
Communication with Mastercard
The data exchange with Mastercard is automatic as Uniconta is the Data Provider. Read more about the Data Provider Agreement
here
Sending files
Uniconta searches the File Archive several times a day. Files that have a check mark in the Export column and where Status = Pending will be sent to Mastercard.
Receiving files
Uniconta searches for return files at Mastercard several times a day. The files are placed in the File Archive and can then be loaded manually by pressing the Import button under Payment suggestions.
File archive
All files exchanged with Mastercard are archived under File archive. File archive can be opened via the menu in Payment suggestions.
The exchange of files takes place automatically in Uniconta.
Here is an overview of the columns.
| Column |
Read/Write |
Description column |
Note |
| Created |
R |
Date the file was received/sent |
|
| Vendor number |
R |
Creditor number |
Unique identification of the company at Mastercard |
| Export |
R |
Marking for receiving/sending |
Files sent from Uniconta to Mastercard will have a markup |
| File name |
R |
The physical file name |
|
| File-Id |
R |
A unique file id |
|
| Payment format |
R |
Format (File formats for payment methods) |
An indication of which payment method each file relates to |
| Status |
R |
Status can have the following values:
Pending The file has not been read
Ok The file has been handled correctly
Error A flag that there are Payments/Mandates that need further attention |
|
| Status information |
R |
Is a log of activities |
|
Here is an overview of the buttons in the menu
Button - Show/Hide Status information
The status information can be read directly in the column, but for a better overview it can be displayed at the bottom of the screen.
Button - Export file
The files can be read out if you want to view the content.
Button - Show
Here you can view the content of the individual files.
Description of files (Deliveryear service)
Sending - Mandates
Enrollment of mandates has the following mask
Mandate_NetsLS_<yymmdd_hhmmss>_Register
Unsubscribing mandates has the following mask
Mandate_NetsLS_<yymmdd_hhmmss>_Unregister
Changing mandates has the following mask
Mandate_NetsLS_<yymmdd_hhmmss>_Change
Sending -Collection/Payment
The files have the following mask
NetsLS_< yymmdd
>_ <Unique file ID>
Receiving
Uniconta receives the following files from Mastercard Leverandørservice.
T-file
Is a transmission file that only indicates whether the sent files have been correctly received by Mastercard. The file will only be shown if errors have been detected in the delivery. The file is received immediately after files have been delivered to Mastercard.
V-file
Is a validation file. It is a readable text file that provides general information about the transferred transactions. It will say 'Error' in the status column if any of the transferred transactions are in error. This file is also received immediately after the transfer to Mastercard. The file can be read by pressing the 'View' button or you can also choose to read it from the File Archive.
D-file
is the data file that contains information that is updated in Uniconta. The file will be loaded around 19:00 on weekdays. The file contains two types of information:
Receipt and remarks(690)
This delivery type is sent by Mastercard to the data provider when Mastercard has received deliveries with debtor information.
The file contains information about Mandates and Payments.
All the information in this file will be updated on the individual Payments or Mandates. In some cases, the status will change on the Payments. All information will be written in the log of the Payment/Mandate.
Below are some examples of status updates that can be received on a Mandate.
Below are some examples of status updates that can be received on a payment.
Payment information (602)
This type of delivery is sent by Mastercard on the payment date when the requested payments have been completed. Mastercard has previously been notified of the payments in a delivery with debtor information.
The file contains information about Mandates and Payments.
Below is an example of a payment.
The invoice was sent on d. 20.06.18. The payment has been completed on d. 21.06.18
Description of files (Betalingsservice)
Sending - Mandates
Registration of mandates has the following mask
Mandate_NetsBS_<AccountingId>_<Accounts payable number><yymmdd_hhmmss>_Register
Unsubscribing mandates has the following mask
Mandate_NetsBS_<AccountingId>_<Accounts payable number><yymmdd_hhmmss>_Unregister
Changing mandates has the following mask
Mandate_NetsBS_<AccountingId>_<Accounts payable number><yymmdd_hhmmss>_Change
Sending -Collection/Payment
The files have the following mask AB_PBSXML000<yyyymm><cvr number><Unique ID>PROD
|
Description |
Length |
| AB_PBSXML000 |
LayoutID |
12 |
| YearMonth |
YYYYYMM, Date sent to Mastercard |
6 |
| CVR number |
CVR number for Data Supplier (will always be Uniconta) |
8 |
| DeliveryId |
<Serial number><AccountingId> |
10 |
| PROD |
Information for Mastercard |
4 |
Eksempel: AB_PBSXML000201903332669280012100256PROD.zip
The file will always be compressed - hence the .zip extension.
Receiving
Uniconta receives the following files from Mastercard Betalingsservice.
T-file
Is a transmission file that only indicates whether the sent files have been correctly received by Mastercard. The file is received immediately after files have been delivered to Mastercard. Please note that Uniconta will receive the file with a maximum delay of 60 minutes.
V-file
Is a validation file. It is a readable text file that provides general information about the transferred transactions. It will say 'Error' in the status column if any of the transferred transactions are in error. This file is also received immediately after the transfer to Mastercard. The file can be read by pressing the 'View' button or you can also choose to read it from the File Archive.
Example of error in file from Betalingsservice
If you get the following information in the Accounting journal (BS: Could not find original invoice), it is because Uniconta cannot find the invoice (the open entry) related to the payment from Mastercard. There can be several reasons for this.
If you have a Total solution, it may be because the customer has entered incorrect information from the payment card. In the example below, a customer has entered incorrect information. If you get the above error in the Accounting journal, you will see an error description under File archive.
In the File Archive, you can see that this 602 file has a payment that cannot be found in Uniconta. The Mandate ID in this case looks mysterious, as the length of the ID differs greatly from how the Mandate ID is created in the current accounting. This is a sign that the customer has probably entered incorrectly.
In some cases, Mastercard can help find the customer if a digit is entered too much or similar, but in this case Mastercard cannot see who made the payment. Therefore, only the creditor's bank can see it via a so-called Archive Reference. They must therefore contact their own bank.
Below is the content of the 602 file. It clearly shows that this deposit is different from the other deposits.
The problem can also arise if a company sends out invoices with a payment card and at the same time collects via Betalingsservice with the same FI creditor number and the notification is set to Mastercard.
Read more in the section
'Creating/Changing FI creditor'
In this situation, all payments will be included in the 602 file from Mastercard. This means that payments that customers have made via the invoices sent by the company itself will also be included in the 602 file. The problem is that Mastercard does not know the Payment ID on the payment card and therefore cannot translate the code. These payments will therefore fail when loaded into Uniconta.
The solution to this is also described in the link above.
Example of error in file from Leverandørservice
In this example, a V-file has been received from Mastercard with the status 'Error'. It is therefore recommended that you look in the file itself. Extract the file using the 'Export file' button and then open the file in a text editor.
Here you can read that the charge of 40,937.00 has been rejected as the total charge amount per day exceeds the maximum allowed.
D-file
is the data file that contains information that is updated in Uniconta. The files will be loaded after 19:00 on weekdays. There will be two types of files:
602 - This file contains payment information
603 - This file contains appointment information. Registration and deregistration of appointments.
686 - This file can be ordered from Mastercard if you wish to receive it. Read more about the file
here 
Here is an overview of the columns.
Status 'Pending'
The 'Pending' status can also be used to search for payments. Use the 'Change status' button to change the status of the selected payments. Payments with status 'Pending' will not be included in the payment run.
The payments in the example above have been grouped into four groups.
The first three groups will result in six charges. The last group 'Deselected' contains all the payments that will not be output in the payment file.
Below is a description of the groups. Groups are grouped according to a Collective Payment ID, which is a combination of the unique key (<Debtor number>-<Payment date>) that characterizes the individual payments in the group.
Collective payment: -
The payments in this group will be handled individually. This means that four collections will be created for the four debtors.
Collective payment: 100100-20180713
Debtor 100100 has six collections with the payment date 13.07.2018. A collection of DKK 29,715.00 will be created. The payment will be executed on d. 13.07.2018.
Collective payment: 100106-20180713
Debtor 100106 has two invoices with the payment date 13.07.2018. A collection of DKK 2,000.00 will be created. The payment will be executed on d. 13.07.2018.
Collective payment: Deselected
All payments that are incorrect or otherwise do not meet the selection requirements are placed in the 'Deselected' group. These payments will not be output in the payment file.
TransfertoAccountingjournal
Uniconta keeps track of which payment lines have been collected when transferring to Accounting journal.
In the example, 6 lines are transferred to the accounting journal. The invoice numbers related to payment are listed in the 'Offsets' column and will automatically offset the invoices when posting.
If you have a Total solution, it may be because the customer has entered incorrect information from the payment card. In the example below, a customer has entered incorrect information. If you get the above error in the Accounting journal, you will see an error description under File archive.
In the File Archive, you can see that this 602 file has a payment that cannot be found in Uniconta. The Mandate ID in this case looks mysterious, as the length of the ID differs greatly from how the Mandate ID is created in the current accounting. This is a sign that the customer has probably entered incorrectly.
In some cases, Mastercard can help find the customer if a digit is entered too much or similar, but in this case Mastercard cannot see who made the payment. Therefore, only the creditor's bank can see it via a so-called Archive Reference. They must therefore contact their own bank.
Below is the content of the 602 file. It clearly shows that this deposit is different from the other deposits.
The problem can also arise if a company sends out invoices with a payment card and at the same time collects via Betalingsservice with the same FI creditor number and the notification is set to Mastercard.
Read more in the section 'Creating/Changing FI creditor'
In this situation, all payments will be included in the 602 file from Mastercard. This means that payments that customers have made via the invoices sent by the company itself will also be included in the 602 file. The problem is that Mastercard does not know the Payment ID on the payment card and therefore cannot translate the code. These payments will therefore fail when loaded into Uniconta.
The solution to this is also described in the link above.
Example of error in file from Leverandørservice
In this example, a V-file has been received from Mastercard with the status 'Error'. It is therefore recommended that you look in the file itself. Extract the file using the 'Export file' button and then open the file in a text editor.
Here you can read that the charge of 40,937.00 has been rejected as the total charge amount per day exceeds the maximum allowed.
D-file
is the data file that contains information that is updated in Uniconta. The files will be loaded after 19:00 on weekdays. There will be two types of files:
602 - This file contains payment information
603 - This file contains appointment information. Registration and deregistration of appointments.
686 - This file can be ordered from Mastercard if you wish to receive it. Read more about the file here