I am working on accounting application and have one dilemma on how to treat Account Payable & Receivable with respect to them actualy been or not payed.
For example, Company A sells Product B to Customer X. They issue an invoice, send to Customer X and at that point of time, the transaction is shown on Account Receivable with notion its for Customer X and other info (date, etc...).
The question is, what happens when Customer X actually pays for it? Should that transaction still be visible in Account Receivable or removed from it?
I am interested in it from accounting point of view.
Once a payment is applied on this invoice, Accounts Receivable should be credited and its balance for this customer should be 0
Related
Procedures
Names of existing procedures to reference .Job and SSIS information if applicable
none
Business Background
Proactive contact strategy to clients with Saving Accounts to open a Credit Card Account.
Program Objectives
Contact BOfA clients with a Saving Account to encourage them to open a Credit Card account.
Dependencies
None
Follow-up Metrics :
none
Requirements
• Audience requirements
Clients that have Saving Account but no Credit Card Account with the bank
• Execution requirements
Description of how and when the campaign should be executed.
Execute Campaign Monthly: Leads targeted to load the first Monday of the month and remain open until first Sunday of the month.
• Output/Detail fields Section
The following detail fields apply to all outbound campaigns:
Detail Field 1: DOB
Detail Field 2: Age of the Saving Account
Detail Field 3: Saving account balance
Exclusions Rules
Standard Exclusions/ Mandatory Scrubs – All Client Campaigns (Only the ones in Bold)
Select Description
DSCD Primary account holder is deceased
AML Money Laundering Alert present
NRC HH has a non-resident alien
FRGN HH has a non-US address
HZIP HH has a zip code in a FEMA disaster area
Dedupe
HH Level De-dup (when multiple accounts in the HH qualify for the same campaign:HH level
De-dupe (Primary account)
NOPN Account we do not have a phone number
Custom Exclusions
Include accounts that have more than 1000 in saving – exclude accounts that have less than or equal to 1000 in saving
Include clients that are at least 25 years old -- exclude clients that are younger than 25 years
If a client already has a Credit Card account, he/she should not be targeted -- include clients who have a saving account but not a credit card account
I was trying to build select statements and create final table,
create a merge statement and create stored proc
I have the following business model and I'm not sure is it possible to manage it using IAP.
The user can create and share with others premium content. The rest of users may subscribe "the content" to get an exclusive access in a specific period of time. Price list might be the same per each specific groups of products.
Example:
User A1 creates premium content P1 (price 0.99$ per month sub)
User A2 creates premium content P2 (price 0.99$ per month sub)
User A2 creates premium content P3 (price 0.99$ per month sub)
User A3 subscribe (auto-renewable) to P1, P2, P3 (A3 is charged three times every month)
User A4 subscribe (auto-renewable) to P2 and P3 (A3 is charged twice every month)
The problem I met so far:
1) When the premium content is adding dynamically, each new product has to be added to iTunes List. It's not scalable what if there are 10000 different premium products?
2) What if I'd just define the list of all possible auto-renewable price tires, for example, 10 different tires - it's still not possible to charge user more than once for a content using the same product_id.
Generally, It could be handled by custom server solution supported by Paypal or Stripe. The problem is that selling digital good requires that the In-App Payment need to be used.
Adding 10,000 different IAPs is not scalable. Each new IAP also needs to be approved by Apple so this doesn't work.
It would be possible to create multiple subscription products at different prices. If you put them in the same subscription group, you would be able to initiate a new IAP to migrate the user from tier to tier without a gap in billing. I would suggest selling a smaller number of tiers (0-5, 5-10, 10+) rather than forcing the user through an upsell experience every time they added a single new subscription.
On the getting started page for Apple Pay, it says that Apple Pay supports "partial shipments." How is this implemented in practice? I know how to get a token from a successful PKPayment. Once I get that token, how do I use it to implement multiple sub-order payments through my payment gateway?
For example, say the user validates a total $100 purchase through Apple Pay of two separate suborder shipments ($40 and $60 each) and I now have an associated token for the $100 order. Because of restrictions on some networks, we can't capture each payment until the associated item has been shipped, and they ship at different times.
Do I have the ability to authorize and capture payments of any amounts using that token?
What is the best approach to authorizing and capturing those sub orders?
Do I auth for the total ($100) and then auth for each sub total ($40, $60) at shipment and then capture for each sub total? If so, then I will be potentially authorizing more than the necessary total ($200), and that doesn't seem right. Is it valid to just skip auth for the total, auth for each sub total, and then capture the sub totals as they ship?
You can't capture an authorization more than once. For stripe you would need to save the token to a customer, and charge the customer for each shipment separately. This isn't only the best way it is the only way to do it.
Once you have a token and attach it to the customer object in stripe, you have the ability to charge it at any time & any amount up until the expiration date or if they remove the card from their apple pay account, like you would any other card regardless of the initial authorization.
The rest of your questions will vary by opinion as there are different ways of doing it, but here is how I would charge this type of order. I think this method benefits both the business and the customer, in addition to keeping stripe/apple happy. This isn't apple pay specific, I would treat most orders with these requirements the same. Also keep in mind apple pay supports it, but it is not required. You can collect all up front regardless of shipment dates.
Generate token from PKPayment for $100
Create customer(if needed) & add token to customer
Create charge against customer using that card for $100 without
capture
Within 7 days assess expected shipping dates.
Once assessment is complete immediately capture only the amount
expected to ship within a week on the initial charge. In your
example this is where I would capture $40 for the first charge. If
nothing is expected to be captured issue a complete refund.
Any shipments beyond the 7 days, create individual charges for the
shipments using the customer object, not the token. Again in your example this is when the $60 shipment goes
out charge that here.
As long as the second shipment charge doesn't happen to go out earlier than the 7 days this would prevent any authorizations overlapping resulting in holds of more than the initial amount at any given moment. I would treat almost any transaction like this apple pay or not.
I know this is supposed to be simple but I'm having trouble coming up with a good, simple setup.
I'm building an app for a school. The school charges for things like pre-registration fee, supply fees, monthly enrollment, etc.
The most important aspect of billing is the monthly enrollment. Let's say it's $50 per month. I want to setup recurring billing (maybe with Stripe), but some people might choose to pay cash, or check or one-time credit card charge, instead of an automatic monthly withdrawal from their account.
Also, fees other than monthly enrollment, such as supply fees, books and such.
I was thinking about creating an Invoice setup, which I already have from another app (kinda like Freshbooks or Blinksale, [Item, LineItem, Tax, Invoice, Payment, etc]) but I thought that might be overkill.
So how would you set this up? Important points...
Ability to charge a monthly recurring fee and other one time charges
Able to track if item is due or if it has been paid
Track if monthly enrollment has been paid, MAKING A RELATIONSHIP between the payment and the monthly enrollment
I would just have a payments model. It would have a frequency (monthly, quarterly, half-yearly, yearly), payment status(paid or pending) and due date and type of fee(pre-registration, supply, etc)
If a guy opts one time payment in beginning, he would have all payments inserted and due date would be the current date and all the statuses would be paid.
If he opts for some fees to be paid monthly, he will have 12 records in payment table with frequency 'monthly'. The due date would be spaced one month apart each. The status of the last 11 records would be pending.
You can now track the list of payments whose due date is within next one month and take appropriate action.
I'm developing an app in Ruby on Rails where companies buy advertising campaigns. First they buy credits to their account on my site, then they buy the campaigns with the credits. The thing is the campaign is payed per view/click. A company reserves a budget of credits for each campaign and these reserved credits can't be used to buy other campaigns with. When a campaign ends and not all credits are used they will be un-reserved and available to buy more campaigns for.
How do I structure the models in the database and how to move/reserve/un-reserve the credits in order to periodically check for any credits that should be un-reserved in a background process?
Have a client/campaigns relationship. Each client has a number of credits. Each client campaign can withdraw credits from the client. As a campaign is viewed/clicked it withdraws credit from the client campaign.
A process periodically checks for lapsed campaigns. When it finds one, any remaining credits are deposited back to the client's main account.
All the money is kept in the company's account all the time. The goal is then to dynamically calculate how much of the funds that are reserved and how much that are not. This can be done if every campaign have a reserved amount attribute and a used amount attribute. When a user clicks on the campaign I withdraw money from the companies account and add them to the campaigns used account.