Using OHIPay

Bring your MDBilling history into OHIPay.

OHIPay can import a recognised MDBilling.ca Excel export into read-only patient billing history. Review the file before saving, see which rows need attention, and keep historical claims separate from claims you are preparing to send.

What this import is for

The import brings prior billing into a patient's history so you can see earlier service dates, codes and amounts alongside later work in OHIPay. Imported history also informs duplicate and yearly-limit checks. These checks are advisory; an import does not establish whether a service is payable.

This is a history import, not a transfer of an active submission queue. An unpaid claim in the spreadsheet does not become a new claim ready for OHIPay to send. Keep the previous system's records and remittances available while you resolve any outstanding claims.

References: OHIPay features and product workflow

Start with a supported export

The supported format is an MDBilling.ca Excel workbook with the .xlsx extension. CSV, PDF, screenshots and exports from other vendors are not supported by this billing-history importer. A separate patient-list import is a different workflow.

Keep the original column headings. The importer recognises the MDBilling layout using MD ID, Accounting ID, Service Code and Service Date. It reads text dates using that format's day/month/year order. Do not rearrange dates or rename headings just to make an unrecognised file pass.

Use the export for the physician whose OHIPay account will receive the history. Rows billed under another physician's number are skipped. If you are unsure which export to obtain, ask support about the required layout before changing the file.

References: OHIPay features and product workflow

Preview, then confirm the import

  1. In OHIPay on your computer, open Tools → Import billing history.
  2. Under Choose an export file, select the MDBilling .xlsx workbook. OHIPay reads it and shows a preview; choosing a file does not save the claims.
  3. Check Recognised: MDBilling.ca and the service-date range. Compare the Claims, Service lines, Patients and New patients counts with the history you intended to import. One claim can contain several service lines, so those counts need not match.
  4. Read Rows needing attention before proceeding. Review both skipped rows and any advisory labelled still imported. If the dates, physician or layout look wrong, use Cancel and check the source export.
  5. Select Import … claims only after reviewing the preview. This is the step that saves the imported history.
  6. Check the result for imported claims, new patients, matched patients and any reported exceptions. Then check Past imports for the file, claim count, patient count and date range.
  7. Open a relevant patient's billing history to review the imported entries. Keep your original export and prior reports available for reconciliation.

References: OHIPay features and product workflow

Understand the import's boundaries

What the billing-history import does and does not do
AreaWhat OHIPay imports or usesLimit to plan around
Claim historyOriginal claim identifiers, service dates, diagnosis, service codes, quantities and available billed/paid amounts and MOH codes.History is read-only; these records do not enter the sending queue.
PatientsMatches existing patients and can create patient records for eligible new entries.An existing patient's demographics are preserved, not overwritten by older export values.
Repeat exportsSkips an already imported claim using the physician, source vendor and original claim number.Re-importing is not an update or reconciliation of a previously imported claim with changed amounts.
Billing checksUses imported history in duplicate and yearly-limit checks.Warnings depend on the history available and do not guarantee complete duplicate detection or payment.
Financial reportingKeeps imported details available in patient history and records the import batch.Does not add imported amounts to dashboard or financial-report totals, rebuild remittance reports, or enter active claim lists or claims CSV exports.

References: OHIPay features and product workflow

Read exceptions before repeating an import

Rows needing attention explains why particular rows were excluded or handled differently. Examples include another physician's billing number, an unreadable service date, a missing service code, an unusable patient identifier or a claim imported earlier. The importer accepts supported OHIP and reciprocal-billing rows; private-pay and WCB billing are outside its scope.

A hospital number missing from OHIPay's facility list is different: the row can still import without a facility. The screen marks that advisory as still imported. Do not treat every item in this list as a lost claim.

If confirmation is interrupted by a connection error, check Past imports and the patient's history before trying again. The import may have saved even if the response did not reach your screen. An overlapping export skips earlier imported claims, but it is still worth checking the completed batch instead of repeatedly uploading on assumption.

References: OHIPay features and product workflow

Separate the switch from your next submission

Agree on which services will first be billed in OHIPay and which outstanding claims remain under review from the previous system. Check the old submission and payment records before creating a claim in OHIPay for work that may already have been sent. Importing the history does not resend those services.

History import and the MOH connection are separate setup steps. Finish the account and connection workflow before sending new claims; a successful import does not prove the account is ready to submit. Support can walk you through the setup and the first claim review.

For your new work, distinguish Saved claims, Ready to send and Sent to MOH. Review the displayed automatic-sending setting as part of the transition. Use current pricing and the cost calculator below to compare ongoing software fees separately from your reconciliation work.

References: OHIPay features and product workflow · OHIPay pricing

Illustrative workflow · fictional example

An overlapping export, without another submission

Imagine that you import a spring MDBilling export, then later choose a broader workbook that also contains the same spring claims. This is a fictional workflow, not a customer result.

The preview identifies claims imported earlier and reports them as skipped. New eligible claims can be saved after you confirm. Neither group is sent to MOH by the import. If you expected an old claim's payment amount to change, stop and review it: the overlap check skips the original claim rather than refreshing it from the newer export.

Questions about this workflow

Can I import a Dr.Bill, CabMD, CSV or PDF export?

The billing-history importer currently recognises MDBilling.ca Excel .xlsx exports only. Ask support about your source format before attempting a conversion. Renaming a file or its columns does not make another vendor's export supported.

Will imported unpaid claims be sent to MOH?

No. Imported claims are read-only history and never enter OHIPay's submission queue. Review outstanding claims against the previous system's submission and payment records before deciding on the next action.

Will an older export replace a patient's current card or demographics?

No. The import preserves existing patient demographics. It can create new patient records for eligible entries, while matching eligible history to patients already in OHIPay.

Will my historical revenue appear in OHIPay's dashboard totals?

The import does not add those amounts to financial-report or dashboard totals. Historical billed and paid details remain in patient history and can inform automatic-premium progress. Original Ministry remittance files are a separate source used by financial reports and Insights. Keep the prior system's reports for reconciliation.

What if I select the same export twice?

Claims already imported under the same physician, vendor and original claim number are skipped. Check the preview and Past imports. This duplicate check does not update earlier imported claims when their source values later change.

References and scope

This guide describes OHIPay's product workflow as checked on October 12, 2026. Product references describe the software; Ministry references explain the applicable external process. A saved, imported or sent claim is not evidence of Ministry approval or payment.

  1. OHIPay features and product workflow

    Product reference. The import steps and limits in this guide were checked against OHIPay's import screen, vendor-format definition, import service and separation from claim submission on October 12, 2026. The financial-report and premium-progress distinction was rechecked against the report and Insights services on October 20, 2026.

  2. OHIPay pricing

    Current product pricing and inclusions. Plan your software cost separately from the history import and the work needed to reconcile outstanding claims.

For a different screen or an unexpected result, contact OHIPay support with the screen name and the message shown. Do not send health-card numbers or patient records through a public contact form.

Help with your workflow

Check the fit before you move your billing.

Request access with your physician details. After review and approval, we email an invitation to set your password and help arrange your Ministry connection. For import help, request a walkthrough of the supported export, preview and history limits before moving your records.

Explore OHIPay features · See current pricing