Skip to content
Guide

Search the Guide

Enter a query to search the Guide.

Íslenska
Menu
On this page

Update national-register information

You can retrieve the latest changes from Ferli and update existing cards. An update can change a name, address, postcode, city and blocked status, so check the result before continuing to use the card.

Scenario

Dæmi ehf. has moved from Dæmisgata 10 to Dæmisgata 20. You want its customer card to use the new address registered by Ferli.

Before you start

Configure the file connection and identification fields. An update file adds or refreshes rows; a base file rebuilds the national-register list.

Warning

Fetch Update File updates matching customers and vendors immediately. Do not treat it as an import that always waits for approval.

Walkthrough

  1. Open RdN National Register List through Business Central search.
  2. Choose Fetch Update File. With File as the data source, the file is retrieved and matching cards are updated.
  3. Select the Dæmi ehf. row if register data is retained. Compare the row with BC Information and open the relevant card to verify the change.
  4. Open National Register Setup and the Update Logs action to see the numbers of updated customers and vendors.

Existing register row and BC Information

Update logs with the created-by user hidden

Result

The customer card for Dæmi ehf. shows Dæmisgata 20. If the same kennitala is also on a vendor card, that card can be updated too. Rows that match no cards do not create new cards during the update.

Accept or reject stored rows

To apply information from a stored row, select it and choose Accept Selected. The action updates both the matching customer and vendor, if both cards exist, and marks the row Processed.

Update actions, shown without accepting or denying rows

Accept all covers all unprocessed national-register rows, not just selected or visible rows. Deny Selected marks the rows as processed without changing cards. It does not undo changes already made. A processed row can still be accepted individually, and a new import can make it unprocessed again.

Certain development codes, including those for dissolution or merger, can block cards for all transactions. Updating does not automatically remove an existing block. See Help.

Base files or manual import

Fetch Base File deletes all previous rows from the national-register list before reading the new file. It does not delete customer or vendor cards. Confirm only if you intend to rebuild the list. You are then asked whether to read the retrieved file into the table; when data is retained, you are also asked whether to update the cards. With data storage disabled, cards are updated directly without that final question.

If Ferli provides you with a file, choose Upload Update File or Upload Base File and select it. Both actions update matching cards. Uploading a base file requires confirmation that all previous register rows will be deleted. Do not use it for an ordinary update file.

What can go wrong

If the list is empty, check Do not store any data; cards may still have been updated. If acceptance actions are missing, open the list through search rather than from the customer or vendor list. See Help.