Invoices

Before an invoice can be checked, paid, or disputed, it first has to be collected — and that is the part most teams underestimate. Every pipeline publishes its invoices on its own Electronic Bulletin Board (EBB), and EBBs are not built to make retrieval simple. What should be a routine download becomes a recurring, manual chore across dozens of portals.

Why getting invoices off the EBB is the hard part

• Each pipeline’s EBB has its own portal, credentials, and layout to navigate.
• Invoices are posted on different schedules, so someone has to keep checking for them.
• Statements arrive in inconsistent formats — PDF, CSV, or proprietary layouts — often one file at a time.
• A missed or late-retrieved invoice can mean a missed deadline to contest a charge.
• The effort compounds with every pipeline you add.

How CORTEX retrieves your invoices

CORTEX takes the manual collection off your team’s plate, pulling invoices from each pipeline’s EBB automatically so nothing is missed and nothing waits on a person to log in.

• Connect — CORTEX integrates with each pipeline’s EBB, so invoices are retrieved without manual logins.
• Retrieve — new statements are downloaded as soon as they are published, across every pipeline, on schedule.
• Normalize — invoices are captured in a consistent, structured format regardless of their source layout.
• Centralize — every invoice lands in one place, ready to review, export, or push into your ETRM.

What you get

• Every invoice collected automatically, the moment it is published.
• No more logging into portal after portal to hunt down statements.
• A complete, centralized invoice record across all of your pipelines.
• The same fast onboarding, subscription pricing, and SOC2-grade security as the rest of CORTEX.

Reconciliation, once your invoices are in

With every invoice already retrieved and centralized, reconciliation becomes a natural next step rather than a separate project. Because CORTEX also manages your actualized volumes and pipeline tariffs, each invoice can be matched against booked volumes and the applicable rates and fuel charges — with any mismatch surfaced as a clear, AI-assisted exception that ties back to the underlying volume or rate, and the full reconciliation logged for compliance and dispute support.