Advanced Fraud Academy
Track 5: Operations & Compliance › Lesson 4 of 5
~9 min read
What you'll learn
  • What the Decision File is and why it matters
  • The difference between manual and automated decision processing
  • The questions to ask your vendor and your core about Decision File support
  • Why this is the most common integration sticking point

The Decision File and core integration

What the Decision File is.

When a business client decisions an exception (pay or return), that decision has to get back to your core so the transaction is processed correctly. The Decision File is how that happens. It's a file, generated after the decision cutoff, containing the details of every decisioned exception — formatted so your core can ingest it and process transactions automatically.

It can typically be delivered by email, secure file transfer, or API, and modern platforms can also make decision data available in real time via webhook.

Manual vs. automated processing.

Without Decision File automation, someone at your FI manually applies each decision to the core every day. With a small program that's tolerable. With a large or growing program it becomes a real operational burden — and it's a frequent reason larger FIs hesitate on Positive Pay.

With Decision File automation, the file flows to the core and transactions process without manual intervention. Getting to automation is one of the highest-value integration outcomes in a Positive Pay deployment.

The questions to ask.

Ask your fraud vendor:

  • How is the Decision File generated, in what formats, and delivered how?
  • Is the file configurable so we can map it to our core's requirements?
  • Is real-time decision data available, not just an end-of-day file?

Ask your core provider:

  • Can you ingest a third-party Decision File and process transactions from it automatically?
  • What does that integration cost and how long does it take?

Why it's the common sticking point.

Decision File integration is the single most recurring challenge in Positive Pay deployments. The reasons: it requires the core to do work, core providers don't prioritize it unless multiple clients ask, the file format has to be mapped precisely to each core, and there can be nuances even within the same core depending on how each FI is configured.

The practical implication: don't assume Decision File automation is included and easy. Make it an explicit line item in your vendor evaluation and your implementation scope. If a vendor or core is vague about the Decision File, that vagueness is your risk.

Do this

Add the Decision File questions above to your vendor and core conversations. Get specific, written answers before you finalize your implementation scope.

What's next.

Lesson 5.5 closes the track and the Academy's curriculum with examiner readiness and reporting.

Self-check

3 quick questions

What is the Decision File?
A A list of enrolled business clients
B A file of decisioned exceptions, formatted so your core can process transactions automatically
C The pricing agreement
D A marketing report
Correct. The Decision File carries each pay/return decision from the PP platform back to the core so transactions are processed correctly — without manual intervention.
Not quite. The Decision File is a file of decisioned exceptions, formatted so your core can process transactions from them automatically — without manual work.
Why is Decision File automation valuable?
A It reduces vendor fees
B It removes the daily manual work of applying decisions to the core
C It's required by examiners
D It eliminates exceptions
Correct. Without automation, someone manually applies each decision to the core every day. That's fine at small scale. With a growing program, it becomes a real operational burden.
Not quite. Decision File automation removes the daily manual work of applying decisions to the core — which becomes unsustainable as the program grows.
What should you do about the Decision File during vendor evaluation?
A Assume it's included and easy
B Make it an explicit line item and get specific written answers on what's automated, manual, and what automation costs
C Leave it to the core
D Ignore it until after go-live
Correct. Vagueness about the Decision File during vendor evaluation is your risk. Make it explicit. Get written answers before you finalize scope.
Not quite. Make the Decision File an explicit line item and get specific, written answers before finalizing scope. Vagueness here is your risk.
← PreviousWhat implementation actually looks like Next lesson →Examiner readiness and reporting