AFAS: Send refunds to AFAS

Turn this on to use a default ledger account for discounts in financial mutations. You need it when you send orders or refunds to AFAS as a financial mutation with the type Extreme. Off by default.

Turn this on to use a default ledger account for revenue in financial mutations. You need it when you send orders or refunds to AFAS as a financial mutation and the data contains no revenue account. Off by default.

Turn this on to use a default ledger account for shipping costs in financial mutations. You need it when you send orders or refunds to AFAS as a financial mutation with the type Complex or Extreme. Off by default.

Turn this on to use a default ledger account for VAT in financial mutations. You need it when you send orders or refunds to AFAS as a financial mutation with the type Recommended, Complex or Extreme. Off by default.

Meant for accounting packages that book refunds on a fixed debtor ledger account. The AFAS refund flow does not use this setting, so changing it has no effect for AFAS. For refunds booked as a financial mutation, use the ledger account settings for revenue, VAT, shipping costs and discounts instead. Leave it at the default (off).

Meant for accounting packages that book refunds on a fixed revenue ledger account. The AFAS refund flow does not use this setting, so changing it has no effect for AFAS. For refunds booked as a financial mutation, use Use default ledger revenue account mapping table instead. Leave it at the default (off).

Use a mapping table to choose the ledger account (grootboekrekening) for discounts when an order or refund is booked as a Financial Mutation. Each row links a value from the incoming data to an AFAS ledger account number. A separate discount line is only made with the Extreme financial mutation method. Off by default.

Use a mapping table to choose the revenue ledger account (omzetrekening) when an order or refund is booked as a Financial Mutation. Each row links a value from the incoming data to an AFAS ledger account number. A revenue account is needed with every financial mutation method. Off by default.

Use a mapping table to choose the ledger account (grootboekrekening) for shipping costs when an order or refund is booked as a Financial Mutation. Each row links a value from the incoming data to an AFAS ledger account number. Shipping costs get their own line only with the Complex and Extreme financial mutation methods. Off by default.

Use a mapping table to choose the VAT ledger account (btw-rekening) when an order or refund is booked as a Financial Mutation. Each row links a value from the incoming data to an AFAS ledger account number. VAT gets its own line with the Recommended, Complex and Extreme financial mutation methods. Off by default.

Determines how an order or refund is split into lines when it is booked in AFAS as a Financial Mutation (financiële mutatie). The other side of the booking always goes to the debtor.

• Simple (default): the whole order on one revenue line.
• Recommended: revenue and VAT on separate lines.
• Complex: a line per order line, each with its own revenue account from the order data or business rules, plus separate lines for VAT and shipping costs.
• Extreme: like Complex, plus a separate line for discounts. Only use this together with an implementation partner.

The ledger account (grootboekrekening) for discounts when APIcenter sends an order or refund to AFAS as a financial mutation. It is used with the financial mutation type Extreme, which books discounts on a separate line. Replace the prefilled value with an account number from your own chart of accounts in AFAS. Prefilled value: 8100.

The ledger account (grootboekrekening) for revenue when APIcenter sends an order or refund to AFAS as a financial mutation. A revenue account is required for every financial mutation type (Simple, Recommended, Complex and Extreme). Replace the prefilled value with an account number from your own chart of accounts in AFAS. Prefilled value: 8100.

The ledger account (grootboekrekening) for shipping costs when APIcenter sends an order or refund to AFAS as a financial mutation. It is used with the types Complex and Extreme: the order line for shipping costs (see Require order line for shipping costs) is booked on this account. Replace the prefilled value with an account number from your own chart of accounts in AFAS. Prefilled value: 1600.

The ledger account (grootboekrekening) for VAT when APIcenter sends an order or refund to AFAS as a financial mutation. A tax account is required for the types Recommended, Complex and Extreme, which book the VAT on a separate line. Replace the prefilled value with an account number from your own chart of accounts in AFAS. Prefilled value: 1600.

Decides what happens when the debtor ledger account mapping table for refunds has no row for a value: Use default (default) uses the default value, Use value keeps the original value and Ignore value leaves the field empty. The AFAS refund flow does not use this mapping, so this setting has no effect for AFAS.

Decides what happens when the revenue ledger account mapping table for refunds has no row for a value: Use default (default) uses the default value, Use value keeps the original value and Ignore value leaves the field empty. The AFAS refund flow does not use this mapping, so this setting has no effect for AFAS.

The code of the AFAS administration (administratie) APIcenter sends orders, purchase orders and refunds to. Enter the code of the administration, not its name; you can use any administration in your AFAS environment. For refunds an administration is always required. In a multi-store setup you can use a mapping table to send each store to its own administration. Default for AFAS: 01.

Turn this on to use a default journal (dagboek) when the data contains none. You need a journal when you send orders or refunds to AFAS as a financial mutation. You enter the code in Value to be used as the default journal id.

The code of the journal (dagboek) in AFAS on which APIcenter books financial mutations for orders and refunds. Use a journal code that exists in your AFAS administration. If no journal is filled in, APIcenter uses journal 40.

Determines what APIcenter creates in AFAS for each incoming order.

• Order (default): a sales order (verkooporder). The articles must exist in AFAS and stock is updated.
• Direct Invoice: a direct invoice (directe factuur), including a stock mutation.
• Quotation: a quotation (offerte), without a stock mutation.
• Financial Mutation: a booking in the general ledger, split according to Use financial mutation method. The articles do not need to exist in AFAS.
• Forecast: a forecast of the expected revenue.

The other options are not supported for AFAS sales orders. For refunds, choose Financial Mutation for a booking in the general ledger; any other choice creates a direct invoice as credit (the AFAS default for refunds). Purchase orders are always created as purchase orders.

Use a mapping table to translate the shipping method from the other application into the value AFAS should receive. The standard AFAS data mapping does not send a shipping method, so this only has an effect when you use the shipping method in the data mapping. Values that are not in the table are handled by What to do with a value that cannot be mapped using the mapping table. Off by default.

The shipping method APIcenter uses when the data from the source contains none. The standard data mapping to AFAS does not send the shipping method itself, so this only has effect when you use it in the data mapping or in business rules.

Turn this on to use a default warehouse (magazijn). For orders sent to AFAS, APIcenter then puts this warehouse on the order and on order lines without a warehouse. If this is on but no warehouse code is filled in, the order is not sent. Off by default.

Turn this on to use a default tax class (VAT code) when the data contains none. You enter the value in Set the value for the default taxclass when products are created. This default is also used for the extra order lines for costs when they have no tax class of their own. Off by default.

When on, APIcenter always uses the default tax class (VAT code), even if the data contains another one. When off (default), the default is only used when the data contains no tax class. For products sent to AFAS, this means every new product gets the default tax class.

Use a mapping table to translate VAT classes or rates from the other application into VAT codes (btw-codes) in AFAS, for example the 21% rate of a webshop into the matching AFAS code. On orders, refunds and purchase orders the code is set per order line; for financial mutations it is also used as the VAT code of the booking. Values that are not in the table are handled by What to do when the mapping can not be made?. Off by default.

The tax class (VAT code) APIcenter uses when the data contains none. Enter the value without a % sign. With a mapping table you can translate the tax values of the source into the VAT codes of AFAS. For products, the tax class is only set when the product is created in AFAS; you change it later in AFAS itself.

Decides what happens when the VAT mapping table has no row for a value from the incoming data.

• Use default: APIcenter uses the default tax id, if that default is switched on; otherwise the field stays empty.
• Use value: the original value is sent to AFAS unchanged.
• Ignore value (the AFAS default): the field stays empty.

For products, AFAS always expects a VAT value, so choose Use default there and set a default tax id.