Magidoc

FinanceRecurringVendorBillSuggestion
Object

A vendor that has billed regularly enough that a schedule would carry its bills into the cash forecast. Derived from posted and approved bills in the trailing twelve months; nothing is written until someone accepts it.

One per vendor, except where a vendor bills on two regular days at two different amounts: a template charges the same amount on every day it names, so that history is offered as two schedules, one per day, each priced on its own runs.

Fields

#

_id

ID !
Non-null

The vendor and the days together, because one vendor can be offered two of these — its id alone names neither.

vendorAccountId

ID !
Non-null

vendorName

String !
Non-null

days

[String !]!
Non-null

Monthly recurrence days in the schedule's own spelling: 1st, 15th, last.

amount

MoneyValue !
Non-null

What one run of the schedule would cost, in the workspace base unit: the median of the latest occurrences of the days it names, an occurrence being every bill the vendor issued on one of those days in one month summed — a schedule generates one bill per occurrence, so a vendor sending two invoices every 1st is priced at what both come to.

billCount

Int !
Non-null

How many bills the suggestion was read from, which is what the panel prints.

monthsSpanned

Int !
Non-null

First billed month through last billed month, inclusive.

nextOccurrence

Date !
Non-null

The first suggested day after today, for the schedule's first run.

documentNumber

String !
Non-null

The vendor's latest reference with its trailing number removed.

paymentTermId

ID

The payment term the priced bills carried, or the workspace term matching their consistent due-date offset. Null where the history states no timing this workspace still has a term for — the schedule dialog's own term field is the person's to set before they save.

Usages

#

References

#

  • Field getFinanceRecurringVendorBillSuggestions from Query