multiRent — Gestion de copropriétésmultiRent — Gestion de copropriétésmultiRent — Gestion de copropriétésmultiRent — Gestion de copropriétés
  • Services
  • Packages
  • Changing managers
  • Partners
  • Our team
  • Blog
  • Contact
  • Français
Portal
✕
20/09/2026
Categories
  • Financial Management
Tags
  • Common Expenses
  • Financial Statements
  • Law 25

Online Condo Fee Payments in Quebec: Bill 25 and PCI

By Muriel Druart, Client services director

Online payment of common expenses is becoming standard in many divided co-ownerships, particularly in the Greater Montreal area. It speeds up collections, reduces errors and simplifies reconciliation. However, in Quebec, implementation must comply with Bill 25 on the protection of personal information, the Civil Code and PCI DSS standards if you accept credit cards. This article guides you through deploying a compliant, secure system that meets the expectations of co-owners and the board of directors (the board).

What “online payment” means in a condo—and what it involves

“Online payment” is not limited to credit cards. Several mechanisms are available, each with implications for the syndicate’s compliance and accounting:

  • Pre-authorized debit (PAD) through the co-owner’s bank account;
  • Bank transfer or Interac with a unique reference for each fraction;
  • Payment portal (third-party provider) by credit card or bank withdrawal;
  • Payment through the syndicate’s management application, integrated with your accounting system.

For the board, selection criteria should include:

  • Traceability of each contribution (common expenses, condo fees and special contributions) by fraction and period;
  • Daily remittances and reports compatible with your financial statements;
  • Security (encryption, access management and logging) and PCI compliance if cards are used;
  • Compliance with Bill 25 for personal information (contact details, IBAN/masked account number, card tokens, etc.).

Governance tip: document your process in an internal procedure, attach it to the financial management plan and mention the preferred channel in your official communications (e.g., AGM notice, syndicate newsletter or portal posting). The minutes may confirm its adoption by the board.

The Quebec legal framework you need to know (C.C.Q. and Bill 25)

Two pillars guide your decisions:

  • Civil Code of Québec (C.C.Q.) — the syndicate’s obligations (keeping books, collecting contributions, retaining supporting documents and managing funds); see the Civil Code of Québec on LégisQuébec.
  • Protection of personal information — Bill 25, which modernizes Quebec legislation, including the Act respecting the protection of personal information in the private sector.

Practical reminders for a syndicate:

  • Transparency and purpose: collect only the data necessary to process contributions. Clearly inform co-owners of the purpose, legal basis (administration of the co-ownership) and recipients (e.g., payment provider);
  • Agreements with providers: your contracts must set out roles and responsibilities (processor/“mandatary”), security, data hosting (ideally in Canada) and retention periods;
  • A register of confidentiality incidents and a notification mechanism in the event of a breach presenting a serious risk of harm;
  • Access and correction: provide a point of contact for co-owners’ requests;
  • Minimization: avoid storing card numbers or cheque scans locally. Prefer tokenization by the third party.

Official resources:

  • Civil Code of Québec (LégisQuébec)
  • Act respecting the protection of personal information in the private sector (P-39.1)
  • Act respecting Access to documents held by public bodies and the protection of personal information (A-2.1)

In practice, the syndicate’s privacy policy must cover the collection of information related to online payment, sharing with the processing provider, the retention period and individuals’ rights. Also plan for compliant archiving of financial documentation so that, when necessary, you can provide a syndicate certificate and clear financial statements for the sale of a condo.

PCI DSS in brief: reduce your risk exposure

As soon as a syndicate accepts credit cards, PCI DSS requirements apply to some extent. The key is to keep card data “out of scope” for your systems.

Best practices suited to a condominium board:

  • Choose a PCI DSS-certified service provider that offers hosted payment pages and tokenization;
  • Avoid collecting card numbers through the manager or the board (never by email, PDF form or telephone without a recorded and encrypted solution);
  • Limit portal roles and access (least-privilege principle), enable multifactor authentication and log actions;
  • Prohibit local export of sensitive data and monitor report downloads;
  • Document a short applicable “SAQ” with your provider (e.g., SAQ A when nothing is processed or stored by the syndicate).

Include these requirements in your internal procedure and, if necessary, in the building’s bylaws when they address permitted payment methods. This will strengthen operational discipline and co-owner confidence.

Accounting, reconciliations and communications with co-owners

For online payment to simplify—not complicate—financial management:

  • Unique references: assign an identifier by fraction (or unit) and by contribution type. Example: “302-CC-2026-10” for October common expenses;
  • Daily bank reconciliation: reconcile the provider’s deposits with the general ledger and record provider fees separately from common expenses;
  • Monthly financial statements: standardize your reports for the board (arrears, receipts and adjusting entries). This will also facilitate AGM and annual budget preparation;
  • Interest and late notices: apply the terms set out in the declaration of co-ownership or the building’s bylaws. Use standardized templates for notices, followed by a formal notice of default if necessary;
  • Retention of supporting documents: keep reports, statements and board minutes confirming decisions. Rigorous record-keeping supports the contingency fund over the long term and provides reassurance during sales.

Communicate clearly with co-owners: registration guide, accepted payment methods, deadlines, treatment of provider service fees and accessibility measures (e.g., offering PAD at no charge). This reduces questions for the manager and prevents misunderstandings.

For co-ownership governance resources, see the RGCQ.

Step-by-step implementation: a model for your board

Here is a seven-step framework that a syndicate in the Montreal area successfully followed to modernize its payments—without disclosing sensitive data or adding complexity to its accounting:

  1. Needs and scope: common expenses, special contributions, access keys/fobs and reservations of common portions (pool, room)—determine everything that will be handled online;
  2. Provider selection: PCI certification, Canadian hosting or equivalent, transparent fees and reports compatible with your accounting software;
  3. Agreements and compliance: confidentiality clause (Bill 25), logging, retention period, audit rights and French-language support;
  4. Accounting setup: chart of accounts, product codes, references by fraction and mapping of provider fees (do not confuse them with common expenses);
  5. Access controls: MFA, “read-only” roles for the auditor or board member responsible for financial statements, and segregation of duties (entry versus approval);
  6. Limited pilot: test with a few volunteer co-owners, validate reconciliation and correct the procedure before the full rollout;
  7. Formal adoption: board resolution, entry in the minutes, distribution to co-owners, update to the privacy policy and, if required, the building’s bylaws (ratification at the AGM).

Remember to align these initiatives with your other obligations (maintenance logbook / EGD, contingency fund planning) so you can present a consistent financial picture at the AGM.

Useful links and services

  • multiRent financial management services
  • Our plans and pricing
  • The multiRent blog (guides and updates)

Official references:

  • Civil Code of Québec (C.C.Q.)
  • Act respecting the private sector (P-39.1)—protection of personal information
  • Access Act (A-2.1)
  • RGCQ—co-ownership resources

FAQ—Online payments in co-ownerships

Can the board require all co-owners to pay by credit card?

Generally, the board may identify a preferred payment method, but it is prudent to offer at least one fee-free option (e.g., PAD or a transfer with a reference). Check your declaration of co-ownership and, if the building’s bylaws are being changed, have the change approved in accordance with the voting rules and record the decision in the minutes.

Can “card fees” be passed on to co-owners?

If a provider charges processing fees, clearly specify how they will be covered (by the syndicate, included in the budget or charged when the service is used). Comply with your declaration of co-ownership and bylaws. When a separate fee is recharged, identify it correctly in the accounting records and inform co-owners in advance.

Does online payment really speed up reconciliation and financial statements?

Yes, if implementation is structured: reference by fraction, daily remittances, separation of provider fees, standardized reports and access controls. This streamlines the preparation of financial statements, presentation at the AGM and communication in the event of late payment.

Updated as of 2026-09-20.

This article provides general information and does not constitute legal advice. Consult a lawyer or notary for your situation.

This article provides general information and does not replace advice from a tax specialist or accountant. Refer to Revenu Québec and the CRA for the exact rules.

Do you manage a condominium in Quebec? Discover our plans or contact us to assess your needs.

Managing your condo building with multiRent

  • How much a condo manager costs
  • Condo manager

Areas served: South Shore · Montreal · Laval · Longueuil · Brossard · Boucherville · Saint-Constant · Saint-Amable · Saint-Jérôme

Share

Related posts

18/11/2026

Condo Accounting: Property Manager or Accountant?


Read more
09/11/2026

Manager-Affiliated Suppliers: Hidden Fees


Read more
19/10/2026

Uninhabitable Unit: Do Condo Fees Still Have to Be Paid?


Read more

Comments are closed.

multiRent — Gestion de copropriétés

Services

Administrative management

Financial management

Operations management

Portal

About Us

The multiRent team

Contact us

Notaries

LinkedIn

RGCQCorporate member of the RGCQ

Resources

RGCQ

CORPIQ

Portal
    Manage Consent

    To give you the best possible experience, we use technologies such as cookies to store and/or access information about your device. Consenting to these technologies lets us process data such as browsing behaviour or unique identifiers on this site. Declining or withdrawing your consent may affect certain features.

    Functional Always active
    Technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
    Preferences
    The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
    Statistics
    The technical storage or access that is used exclusively for statistical purposes. Technical storage or access used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your internet service provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
    Marketing
    Technical storage or access is required to create user profiles in order to send advertising, or to track the user across a website or several websites for similar marketing purposes.
    • Manage options
    • Manage services
    • Manage {vendor_count} vendors
    • Read more about these purposes
    Manage preferences
    • {title}
    • {title}
    • {title}