1.2017.305.0 - Invoice Splitting Improvements, Braintree Update and Minor UI Tweaks

GitHub Release Notes

Features

  • Enable support to split invoices by a monetary value.
  • When splitting invoices enable setting of the purchaseOrder and description per split.

Improvements

  • For Braintree transactions, treat the SETTLED state as indicating a successful payment.
  • Tweaks to the request payment UI.

1.2017.285.0 - Add support for the EPX payment gateway

GitHub Release Notes

Features

  • Add support for the EPX payment gateway

1.2017.271.2 - ChartMogul formulae fixes

GitHub Release Notes

Fixes

ChartMogul

Changed the following formulae:

  • amount = ∑debitsIncTax
  • discountAmount = ∑creditsIncTax
  • taxAmount = ∑debitsTaxOnly

After:

  • amount = ∑debitsIncTax − ∑creditsIncTax
  • discountAmount = ∑creditsIncTax
  • taxAmount = Math.max(0, ∑debitsTaxOnly − ∑creditsTaxOnly)

In all, the following fixes are included:

  • We now report the correct amount (i.e. we report the net, not the gross)
  • We now report the correct taxAmount (i.e. we report the net, not the gross)
  • We now prefer to report $0 instead of negative tax (closest supported representation)
  • We now round up "x minutes" plans to "1 day" (closest supported representation)

We switched over to this new algorithm in Production at 2017-10-01 01:23:18Z.

1.2017.271.1 - Self-service Invoices

GitHub Release Notes

Features

  • Provide additional self-service support. Send payment requests directly to customers enabling their payment details to be captured.

Fixes

  • Ensure the correct usage of the plan's version ID when migrating a subscription to a new plan. This fixes a bug where, after migrating from one plan to another, we wouldn't generate immediate prorated charges.

1.2017.257.0 - UI Tweak

GitHub Release Notes

UI Refinements

  • Added Changelog to UI

1.2017.236.1 - Plan UI Refinement

GitHub Release Notes

Release 1.2017.236.1

UI Refinements

  • Prevent changing the private name of an existing pricing component.

1.2017.236.0 - New Plan API

GitHub Release Notes

Release 1.2017.236.0

Features

  • New Rate Plan API
  • Adds /v1/plans endpoints.
  • Makes it easier to create / update plans, now everything related to a rate plan can be done in one endpoint: PUT /v1/plans. It does both update and create, based on the path (if a plan with a given path doesn't exist we will create a new one). And it can modify a pricing set, including removing pricing components.
  • It is possible to upsert multiple plans in one request, which makes it easier to use a often-convenient model of having all plans stored in one place, a simple json file, which can be upserted to our API every time it is updated on your side.
  • Introduces a concept of path to rate plans. Each plan can be identified by a path, which must consist of N-nested directories and a plan's name and currency (ex. /telecom/broadband/100mbps.USD). The plans's path may now be used instead of its ID or name in all existing API endpoints where a rate plan may be specified.
  • Deprecate old /v1/product-rate-plans API.

1.2017.157.7.1 - Batch Component Value Update Fix

GitHub Release Notes

Release 1.2017.157.7.1 - on Prem only

Fixes

  • When using the POST /subscriptions/{id}/values endpoint and specifying for the change to occur atPeriodEnd it would incorrectly action immediately. This has now been resolved.

1.2017.200.0 - Coupon and Salesforce Sync Improvements

GitHub Release Notes

Release 1.2017.200.0 - US Sandbox

Improvements

  • Ensure that emails are sent correctly when salesforce synchronisation fails or is restarted.
  • Small tweaks to coupons including changes to improve how they are displayed on pdf and html invoices.

Fixes

  • In some cases migrating subscriptions between product rate plans of different lengths with failed payment behaviour of None could yield unexpected results. This has now been resolved.

1.2017.180.3 - Salesforce Sync Performance and Subscription Revive Fix

GitHub Release Notes

Release 1.2017.180.3

Improvements

  • Tweaks to improve the performance and reliability of Salesforce sync

Fixes

  • In some cases when reviving a subscription which was cancelled at its period end a re-subscription charge was erroneously created. This has now been resolved.

No published changelogs yet.

Surely Billforward will start publishing changelogs very soon.

Check out our other public changelogs: Buffer, Mention, Respond by Buffer, JSFiddle, Olark, Droplr, Piwik Pro, Prott, Ustream, ViralSweep, StartupThreads, Userlike, Unixstickers, Survicate, Envoy, Gmelius, CodeTree