Comment 8 for bug 1793802

Continuing from my previous comment... The new money.aged_billing columns can be created during the 3.0 -> 3.1 upgrade as NULL-able so admins may back-fill the data and re-synchronize the columns at their leisure (i.e. not during an upgrade outage).

Given the extra steps required for deploying to a 3.0 system, however, I propose we not back-port the code to 3.0, unless we find the 3.0 -> 3.1 upgrade to be a big issue for a lot of sites, in which case we'll need additional SQL and documentation.