Skip to main content
AFAS Profit is the ERP many MSPs in the Netherlands and Belgium run their own business on: your clients as debtors, the items you sell, the subscriptions that invoice each client every month, sales orders, purchasing, projects and hours, finance, HR and payroll. When a client takes an extra Microsoft 365 licence, the subscription in AFAS has to follow, or you invoice the old number of seats. Neo connects to your AFAS environment through an app connector your AFAS administrator creates, and reads and writes it through the AFAS Profit REST API.

​
What Neo can do with AFAS Profit

  • Read what a client pays for: each subscription line, with its item, quantity, price and start and end date.
  • Keep invoicing in step with licences: when an agent orders a Microsoft 365 seat, or a supplier’s order confirmation arrives on a ticket, the agent raises the client’s subscription lines in AFAS, and the lines you tie to it, such as your workplace package and SLA per user.
  • Find a client’s debtor, open invoices, sales orders and projects.
  • Read any GetConnector you link to Neo’s app connector, standard or one your administrator built, and write the UpdateConnectors you link, when you allow it.
The agent tool, its access profiles and its safety controls: AFAS Profit API.

​
Your debtors are mapped to clients

Neo matches each AFAS debtor to a client in your PSA and keeps the mapping on the AFAS Profit card’s Organization Mapping tab, refreshed on each PSA metadata sync. With the mapping, an agent gets the client’s debtor number on every ticket and reads that client’s subscriptions with one call. Matching starts with the debtor’s name: exact, then after stripping a legal-form suffix (B.V., N.V., Ltd). Next comes the domain of the debtor’s email address against your PSA companies’ domains, and last an AI match for the long tail. A debtor whose name is exactly the name of one PSA company and no other, with no other debtor matching that company, is handed straight to your agents, and so is one you confirm. Any other match shows on the Organization Mapping tab, where you can confirm or correct it. A client you invoice from two administrations is two debtors: confirm both, and agents read both. Anything Neo could not match stays unmapped and visible on the same tab, where you can set the right client by hand. A mapping you set by hand survives every later sync. A mapping belongs to the AFAS environment it was made in, because a debtor number can mean another client in another environment. When you connect Neo to another environment, Neo maps its debtors again, and agents on a ticket use only that environment’s mappings; set any mapping by hand again there.

​
Next steps

Connect AFAS Profit

Create an app connector for Neo in Profit, link the connectors Neo needs, and save its client ID and secret in Neo.