Esta página está traducida automáticamente. Prevalece la versión en inglés. English
Fase 1 · Concienciación Pagos

Un nuevo país es un mapeo de archivo bancario, no un nuevo proyecto X++.

Pagos a proveedores y empleados a través de una sola pasarela, a cualquier banco. El formato de un nuevo país es un mapeo en Azure. Normas IBAN para 89 países.

← All insights
By Solution Architecture team · 23 Sep 2026 · 7 min read Un nuevo país es un mapeo de archivo bancario, no un nuevo proyecto X++.

The payment format that never travels

The first country hard-codes the bank file because "we only pay here". The second country copies the payment journal and asks for a new X++ format. By the time you are paying vendors in Chicago, employees in Lyon and suppliers in Nairobi, you have three payment engines and one logo.

That is the same failure as a template that assumed one tax engine. The payment path is part of the global core. The file the bank will accept is the country layer.

One gateway, any bank

The DisbursementFlow 365 sits on Finance & Operations. It pays vendors and it pays employees. Bank connection profiles cover any bank. Account validation uses IBAN rules for 89 countries. Batches move on maker-checker approval. The file is ISO 20022 pain.001. The status log cannot be edited after the fact.

A new country deployment is a file mapping in Azure for that country's bank formats. It is not a customization, and it is not a second payment journal. India, Australia, the United States and Europe attach the same way Kenya and South Africa do.

Payroll calculates. The gateway pays.

PayrollFlow 365 sits on the global core, on Finance & Operations and on Business Central. Published statutory content covers Kenya, Nigeria and South Africa: earnings, PAYE, returns and the ledger posting. A country configures rates and calendars. It does not stand up a second payroll so that salaries can reach a bank.

Employee payments leave through the gateway, into the same books, with the same maker-checker. A funder report or group pack is complete when it sees those payments.

What we will not build

We will not write a bank format in X++ or AL because a country is new. We will not let a marketplace or a payroll side-system "just send the net" around the payment journal. We will not keep a private integration pattern per entity.

If your programme is about to add a country, ask one question in the steering meeting: is the new bank file a mapping on the gateway you already run, or a development estimate? If it is an estimate, you are buying a local project at a global price.

If you are rolling Dynamics 365 across more than one country, this is the conversation we should have. Reserva una consulta
Hablemos de Soluciones.

Planifica tu hoja de ruta ERP CRM con nuestros expertos.

Reserva una consulta Estima tu retorno
Llamada Reserva una consulta
Software Dynamics
Normalmente responde dentro del horario laboral (EAT)
Hola. ¿Qué intentas resolver? Elige uno y te dirigiremos a la persona adecuada. Quiero ver una demo Soy un cliente existente y necesito apoyo Háblame de la facturación electrónica