BHECS — Oracle AP Positive Pay Implementation & Custom Report Development

Client	BHECS
Industry	Healthcare — Health System
Oracle Version	Oracle E-Business Suite R12
Modules	AP PO PL/SQL
Engagement Period	2020 – 2021
Project Type	Oracle AP Positive Pay Implementation & Custom Report Development
Complexity	Medium · Positive Pay · Bank Integration · Custom Reports · PO Scoping

Executive Summary

BHECS — a healthcare organization — engaged William Delaney Consulting for Oracle AP Positive Pay implementation, custom report development, and PO implementation scoping. The Positive Pay workstream — the most substantive deliverable of the engagement — designed and implemented the bank fraud prevention integration between Oracle AP and BHECS's banking partner: Oracle generates a file of all issued checks, the bank matches incoming checks against that file before honoring payment, and any check not in the Oracle-issued file is flagged as a potential fraud exception.

The custom report suite — AP Invoice Control report (BHECS_AP_INVOICE_CONTROL.rdf, developed through the MEC OptimizeIT engagement) and the PIN Report Rebuild SQL — provided BHECS's AP operations team with operational visibility tools that Oracle's standard report library did not supply at the level of detail required for healthcare AP management. The PO Key Considerations and Estimate document reflects a parallel scoping engagement — assessing the complexity and effort required to extend BHECS's Oracle footprint into Oracle Purchasing.

Engagement Context

Healthcare organizations have distinctive Oracle AP requirements driven by the complexity of their vendor ecosystem: pharmaceutical suppliers, medical device distributors (GPO-contracted and direct), clinical services vendors, and the large operational vendor base (food service, facilities management, IT) that supports a clinical environment. AP payment controls are especially important in healthcare: hospitals process thousands of invoices monthly from hundreds of vendors, creating both a high fraud exposure surface and a high internal control compliance requirement under SOX (for publicly traded health systems) or equivalent healthcare-specific audit standards.

Positive Pay is one of the most effective AP fraud prevention controls available in Oracle EBS. Check fraud — where criminals alter legitimate checks or create counterfeit checks drawn on the organization's accounts — is a significant financial crime that Positive Pay eliminates: the bank will not honor a check that doesn't match the Oracle-issued file. For a healthcare organization processing substantial check payment volumes, Positive Pay represents one of the highest-ROI Oracle AP controls available — implementation effort is moderate, ongoing maintenance is minimal, and the protection against check fraud is near-complete.

The 2020–2021 timing of this engagement — during the COVID-19 pandemic — adds healthcare context. Healthcare organizations experienced significant financial disruption during the pandemic, with increased vendor complexity (PPE procurement from new suppliers), accelerated payment demands, and heightened audit scrutiny. Implementing Positive Pay during this period reflects a finance team that maintained financial control discipline even under operational pressure — a strong organizational signal.

Oracle AP Positive Pay Implementation

Positive Pay Process Design

The BHECS Positive Pay Process Visio diagram documented the complete Positive Pay workflow: the Oracle AP payment run that generates the check batch, the concurrent program that produces the Positive Pay file in the bank's required format, the file transmission process (secure FTP or bank portal upload), the bank's matching and exception reporting, and the Oracle AP exception handling process for checks the bank flags as unmatched. The process design required coordination between Oracle AP configuration, the bank's Positive Pay specifications, and BHECS's treasury operations team who manage the bank relationship.

Positive Pay File Customization

The Modified and Original subfolders within Positive Pay reflect the standard Positive Pay implementation pattern: Oracle EBS includes a generic Positive Pay extract program, but virtually every bank has its own proprietary file format (field layout, record types, header/trailer requirements, check number format) that Oracle's generic extract does not match. The Modified version contains the customized Oracle Positive Pay extract — adapted from Oracle's Original extract program to produce output in BHECS's bank's specific format. Test Files confirm that the customized extract was validated against the bank's format requirements before production deployment.

AP Invoice Control Report

The BHECS_AP_INVOICE_CONTROL.rdf — a custom Oracle Report developed through the MEC OptimizeIT engagement — provided BHECS's AP management with an operational control report covering invoice status, holds, aging, and payment readiness. Healthcare AP invoice control requirements include: tracking invoices in dispute with clinical vendors, monitoring time-sensitive pharmaceutical invoices that carry early payment discounts, and identifying held invoices that require clinical department approval before payment. The custom report delivered this operational visibility in a format calibrated to BHECS's specific AP management needs.

PIN Report Rebuild

The BHECS_PIN_REPORT_REBUILD.sql addressed a custom AP payment or supplier PIN report that required SQL-level reconstruction — typically occurring when a custom report's underlying query breaks due to a database schema change, Oracle patch, or data model evolution. The rebuild required reverse-engineering the report's original intent from the broken SQL, validating the corrected query against current Oracle data, and testing the rebuilt report output against expected results.

PO Implementation Scoping

The PO Key Considerations and Estimate document provided BHECS with a structured assessment of Oracle Purchasing implementation scope: the complexity drivers for a healthcare PO implementation (clinical supply purchasing, GPO contract integration, PO approval workflows for capital vs. operating expenditures), the estimated effort by implementation phase, and the key design decisions that would shape implementation approach. This scoping document positioned a potential future Oracle PO engagement without committing to it — giving BHECS the information needed to decide whether and when to proceed.

Key Deliverables

Deliverable	Type	Purpose
Positive Pay Process Design (Visio)	Process Document	End-to-end Positive Pay workflow from Oracle AP check run through bank exception handling
Custom Positive Pay Extract (Modified)	Oracle Reports (.rdf)	Bank-format-specific Positive Pay file extract customized to BHECS's banking partner specifications
AP Invoice Control Report	Oracle Reports (.rdf)	Custom Oracle AP operational control report for healthcare AP invoice management
PIN Report Rebuild	SQL Script	Reconstructed custom AP report SQL to restore broken report functionality
PO Key Considerations and Estimate	Scoping Document	Oracle Purchasing implementation scoping assessment for healthcare procurement expansion

Consultant Insights

On Oracle Positive Pay Implementation: Positive Pay implementation is straightforward in concept but detail-intensive in execution. The challenge is always in the file format: every bank has its own format specification, and the Oracle generic Positive Pay extract rarely matches the bank's format without modification. The implementation approach — start with Oracle's seeded extract as the Original, modify it to produce the bank's format, validate against the bank's file specification document, and run through the bank's testing process with test files before production — is reliable but cannot be shortcut. Banks that accept files with format errors still process the Positive Pay file, but mis-formatted data produces incorrect matching behavior that defeats the fraud prevention purpose.

On Positive Pay as a Healthcare AP Control: Healthcare AP environments benefit from Positive Pay disproportionately compared to many industries, for two reasons. First, healthcare accounts payable processes high volumes of vendor payments — creating a large attack surface for check fraud. Second, healthcare AP teams manage complex vendor relationships (pharmaceutical distributors, medical device companies, GPO-contracted suppliers) where payment disputes and credit holds are common, creating operational situations where unauthorized checks might not be caught by standard AP review processes. Positive Pay provides a systematic bank-level control that doesn't depend on AP staff catching fraud in their operational review — the bank catches it automatically.

On Custom Report Rebuilding: The PIN Report Rebuild engagement illustrates a category of Oracle technical work that is common but rarely proactively planned: custom reports that break due to Oracle patches, database schema changes, or underlying table structure modifications. The remediation approach — reverse-engineer the original intent, rebuild the SQL against the current schema, validate output — requires both Oracle technical skill (understanding the schema change that broke the report) and Oracle functional knowledge (understanding what the report was supposed to show). Report rebuilding that produces the correct output for the wrong business reason is worse than leaving the report broken.