Dynamics 365 Consultant, Philippines

Business Central or Finance and Operations for a Philippine entity

Microsoft Dynamics 365 is a family of products, and the ERP choice usually sits between Business Central and Dynamics 365 Finance with Supply Chain Management. For a Philippine entity, the parent's choice often decides it. When it does not, I look at the size and complexity of the local operation rather than at the group's ambitions.

Business Central tends to suit sales subsidiaries, small manufacturers and service centers with straightforward finance. The larger Finance and Operations apps make more sense for complex supply chains, heavy intercompany trading or groups that need one global instance with strict controls. Either can be over-engineered for a small local entity.

The local question is the same for both: how are Philippine requirements met? Microsoft localizes its products for a set of countries, and elsewhere relies on partners and AppSource publishers to supply local features. Check which applies to the Philippines for the product you are considering, and ask who maintains the local layer through Microsoft's regular update cycle. A local extension that falls behind an update can stop invoicing at the worst moment. My Microsoft Dynamics consulting page covers the product family in general terms.

When the parent's template meets BIR requirements

Group templates are designed for consistency, and Philippine record-keeping rules sometimes ask for things the template never considered: specific invoice content, controlled numbering by branch, particular books of accounts, withholding on supplier payments and a registration step before the system replaces manual books. Your accountant or tax advisor confirms which apply; I make sure the system answers each one.

My approach is a scenario walkthrough. Local finance staff process real documents in a test company, with the advisor's checklist beside them, and every gap is logged with a proposed resolution: a local extension, a report, a configuration change that does not harm the template, or a manual control. I bring that list to the group design authority early, because late local changes are the ones that cause friction.

Electronic invoicing and sales data reporting to the BIR are expanding too. Because the timetable and scope are still developing, I record what the localization provider or implementer plans to support and keep that as a tracked risk rather than an assumption. For a structured view of this work, see my gap analysis service and the Philippines ERP consultant page.

Captive service centers, USD reporting and PHP books

Captive service centers are a distinctive part of the Philippine economy: entities that exist to deliver finance, customer care, technology or analytics work for their own group. In Dynamics 365 they raise a particular set of design questions.

• Billing the parent. Cost-plus or fee arrangements are set by group tax advisors. I translate the agreed method into allocation rules and recurring intercompany invoices.
• Currencies. Group reporting is often in USD while local statutory books are in PHP. Which currency the entity reports in, and how translation works, is an accounting decision; I configure what the accountants agree.
• Dimensions. Cost centers, programs and service lines need to match both the parent's reporting and local management needs, without exploding into codes nobody uses.
• Controls. Approval workflows, segregation of duties and audit trails need to satisfy group auditors and the local advisor at the same time.

Payroll usually stays with a local provider, posting journals by cost center. I document each rule in the design so the monthly close becomes routine. The solution design page shows how these decisions are written up.

Microsoft partners, licensing and an independent reviewer

Microsoft relies on its partner channel to sell and deliver Dynamics 365. A Philippine entity may work with a partner chosen by the parent, a regional firm, or a local implementer with Philippine experience. Licenses are typically bought through a partner too, which means the same organization often advises on scope, sells subscriptions and bills implementation time.

I sit outside that arrangement, holding no Microsoft partner status and taking no share of subscription revenue, so my review of a proposal looks only at whether it meets the documented requirements at a sensible effort. I check that local features are scoped, that registration evidence is someone's responsibility, that data migration includes reconciliation, and that license counts match the roles that will actually use the system.

During the project I attend design sessions, review configuration and change requests, and run acceptance testing with local finance. Communication is in English, and workshops are scheduled for the overlap between Philippine hours and mine, which covers most of a local working day. Recorded sessions help when parent teams in other time zones need to follow along. For how I support the market overall, see the Philippines overview, and for oversight services, see vendor selection.

Philippine situations that argue against Dynamics 365

Being part of a Microsoft-oriented group does not settle the question for a Philippine entity. I raise these concerns when I see them:

• Small entities with simple needs. A sales office or small service unit may not justify the license and partner cost; a lighter local system feeding group reporting may be enough, with Zoho as one candidate.
• Uncertain local layer. If no one can show how Philippine requirements will be maintained through updates, the risk sits with the local entity.
• Independent local groups. A locally owned distributor with no Microsoft-standard parent may find Odoo or ERPNext a better balance of features and cost.
• Thin partner support for local needs. If the chosen partner has little Philippine experience, budget for a local specialist or pick another route.

An ERP evaluation compares the group-template route with alternatives on your scenarios, so the parent and the local team can decide on evidence rather than habit.