Number of Seats/Users: EzzyBills offers discounts based on the number of users or seats. A higher volume typically leads to a better discount structure, especially for enterprise-level usage.

Commitment to a Long-Term Contract: Discounts are often provided to companies that commit to using the service for a longer period (e.g., 1-year or 3-year contracts). A longer commitment shows EzzyBills that the company is serious and willing to invest in the platform long-term.

No Active Discounts: Companies that are not already receiving other active discounts may have a better chance of qualifying for additional discounts from EzzyBills. EzzyBills reserves discounts for new customers or those not currently under promotional pricing.

Volume or Usage Commitment: EzzyBills offers discounts if you agree to a minimum amount of usage or transaction volume. This could be based on data storage, transactions, or other metrics tied to how much you will use the platform.

Enterprise-Level Negotiation: Companies that qualify as “enterprise” due to their size or complexity (e.g., having large teams, multiple departments, or geographical presence) may be eligible for additional discounts from EzzyBills. Such companies are often in a position to negotiate for better pricing.

Early Renewal or Prepayment: EzzyBills often offers discounts if you renew early or prepay for the entire contract period. This is a common approach to securing a lower price.

Here at Spendbase our internal data shows that EzzyBills is generally seen as a strong time‑saver for accounts payable, with a few important caveats around UX and billing practices.

From what our Spendbase clients report, the main strengths are:

• Big time savings
• Eliminates most manual data entry for supplier invoices
• Bills flow straight into Xero draft bills for approval

• Processing speed is usually “seconds” when everything works as expected

• Data accuracy and depth

• High‑quality OCR
• Line‑by‑line data extraction is praised, especially for detailed GL coding
• Supplier matching via ABN is a standout, reducing duplicate supplier records and coding errors

• Uses the custom supplier name already set in Xero/MYOB, which keeps the ledger clean

• Ease of use and onboarding

• Simple setup and configuration with Xero
• 30‑day free trial makes it low‑risk to test
• File upload and email‑in workflows are straightforward
• Support is often described as fast and helpful when things go smoothly

At the same time, our clients flag some consistent pain points:

• Over‑detailed extraction
• Line‑by‑line extraction can be “too good” for very long invoices

• This may add review overhead if a business usually codes at header level only

• Document limitations

• Handwritten invoices are typically not recognized well

• This can be a blocker in industries where handwritten or low‑quality scans are common

• User experience concerns

• Some clients mention a scrolling screen and invoice image layout that make editing awkward

• Delays from upload to bill creation occasionally cause frustration

• Billing & cancellation friction

• The strongest negative feedback centers on difficulty stopping regular payments
• Perception of “non‑existent” customer service in edge cases creates distrust
• When issues do occur (e.g., “randomly making up information”), correcting them one by one removes much of the time‑saving benefit

From a Spendbase discount and optimization standpoint, EzzyBills tends to deliver high ROI when:

• You process a large volume of typed/printed supplier invoices
• You fully leverage line‑item and GL coding
• You have clear internal controls for bill review and approval

However, we advise our clients to:

• Test with their most complex invoice types during the free trial
• Clarify cancellation terms and support SLAs upfront
• Decide in advance when line‑item capture is genuinely needed vs. overkill

Overall, our internal data shows that EzzyBills can be an excellent value driver, but only when its automation profile matches your invoice mix and your tolerance for occasional cleanup work.