All about AFAS

AFAS: Send price lists to AFAS

Send prices from another system to AFAS as sales prices on a price list, per article.

Updated November 9, 2026

This flow sends prices from another application to AFAS. APIcenter records them as sales prices (verkoopprijzen) of the article on a price list (prijslijst). Use it when another system is leading for your prices.

How it works

  • APIcenter first checks whether the article exists in AFAS. If it does not, the price is skipped with a warning.
  • Each price needs an article number, a unit and a start date.
  • If no price list is given, APIcenter uses the default AFAS price list *****.
  • With the settings below, you can set a default price list or customer group, or map values from the other application to the price lists in AFAS.

What you need first

Tips

  • Do you see a warning that a product was not found? Check that the article number in the other application matches the article number in AFAS.
  • Is the start date or the unit missing in the source data? Add it under Data mapping or with Business rules.

You find all settings for this flow below, each with its own explanation.

Settings

The settings you see in the dashboard, with what each one does.

Default price list group

Customer Settings

The AFAS price list (prijslijst) APIcenter uses as default. When sending orders to AFAS, APIcenter puts this price list on the order lines when the default price list group is enabled. When retrieving price lists from AFAS, this price list provides the base price from which the other prices are calculated. Default: *****, the standard AFAS price list excluding VAT.

Turn this on to use a default price list group. For orders sent to AFAS, the order lines then get the default price list. For Business Pricing (retrieving price lists from AFAS) you also turn this on, because APIcenter needs a base price to calculate discounts, percentages and other prices. Off by default.

Use a mapping table to translate the customer group from the other application into the value the receiving side expects. Without a mapping table, the customer group from the incoming data is passed on unchanged. The standard AFAS data mapping for sending does not fill a customer group, so this only has an effect when you use the customer group in the data mapping. Off by default.

The customer group APIcenter uses when the data contains none. With a customer group mapping table you can translate the groups from the source into the values you need. The value only reaches AFAS when the customer group is used in the data mapping of the flow.

Used by file-based connections, such as CSV files on an SFTP server, where the column headers of a file are translated with a mapping table. AFAS connects through its API and not through files, so this setting has no effect for AFAS. Leave it at the default (Use default).

Use administration mapping table

General flow setting

Notifications frequency

Notifications

Receive Notifications

Notifications

Meant to update the description of price lists that already exist in the receiving application. When AFAS receives price lists, APIcenter only sends the article prices and no price list description, so this setting has no effect for AFAS. Leave it at the default (off).

Skip negativity flip process

Product Settings

Use page size

Run behaviour

Still need help?

Ask the support assistant in your dashboard or create a support ticket.

Go to support