From a conversation a month ago with them, they use the BOI. One thing to note if you are having them create the A/P invoice as well. This became an issue for us with a client. I posted the original Perform Logic on SocialCast so a V/I import into A/P Invoices would reject a duplicate invoice number because the default treatment with V/I (and BOI) is to treat it as an adjustment. So eRequester does NOT do the same treatment when they use BOI (they don't know any better actually because they are not Sage 100 ""savvy"") so you will get adjustments when they import an existing Invoice No. Not saying this dupe situation would even come up but just an FYI in case it does.